# MCP (Model Context Protocol)





<DocImage src="features/mcp/mcp-settings" alt="MCP settings panel" width="1792" height="1280" />

Model Context Protocol (MCP) is an open standard that lets AI agents connect to external tools, services, and data sources. By enabling MCPs in Ideavo, the agent can interact with databases, third-party platforms, browsers, and APIs directly — without you having to manually bridge the gap between tools.

## Benefits [#benefits]

<Cards>
  <Card title="Extended capabilities" icon="<IoExtensionPuzzleOutline />" description="Goes beyond code generation to take real-world actions — browse, query, deploy, and more." />

  <Card title="Direct service connections" icon="<MdMiscellaneousServices />" description="Query databases, APIs, and data sources as part of the same conversation." />

  <Card title="Reduced context-switching" icon="<SiModelcontextprotocol />" description="The agent can read and act on external systems without you leaving Ideavo." />
</Cards>

## Predefined MCPs [#predefined-mcps]

Ideavo ships with a curated set of MCPs ready to enable. No configuration needed — just toggle them on.

| MCP            | Description                                                     |
| -------------- | --------------------------------------------------------------- |
| **Playwright** | Browser automation — visual testing, E2E testing, and debugging |
| **Neon**       | Interact with Neon databases in natural language                |
| **Context7**   | Enhanced context management for AI                              |
| **Kaggle**     | Streamline development using Kaggle datasets                    |
| **Rube**       | Connect AI to third-party apps via Composio                     |
| **Firecrawl**  | Web scraping and data extraction                                |
| **Supabase**   | Connect to the Supabase platform                                |

### Enabling a Predefined MCP [#enabling-a-predefined-mcp]

<Steps>
  <Step>
    Open the 

    **MCP panel**

     from the project sidebar.
  </Step>

  <Step>
    Find the MCP you want and toggle its switch.
  </Step>

  <Step>
    The agent includes that MCP's tools in its context immediately — no restart
    needed.
  </Step>
</Steps>

<Callout type="warn">
  Enabling MCPs increases token usage. Enable only the MCPs relevant to your
  current project to keep usage efficient.
</Callout>

## Start Projects with MCPs Ready [#start-projects-with-mcps-ready]

<Callout type="info">
  On mobile, open the **+** menu during project creation to access the same MCP
  selector.
</Callout>

<Callout type="warn">
  Global MCPs that are already enabled are not shown in the new project selector
  because they are available by default.
</Callout>

When creating a new project, you can choose which MCPs should be included from the start. Selected MCPs are enabled by default as soon as the project opens, so the agent has the right tools available immediately instead of requiring setup after creation.

Click the **+** button in the prompt box on the home page and choose **MCP** to open the MCP selector. The count on the **+** button shows how many MCPs will be included in the new project.

<DocImage src="features/mcp/new-project-plus-menu" alt="The plus menu in the new project composer open, with MCP highlighted and a count of one selected MCP" width="1120" height="756" />

The selector shows available MCPs. The **Global** section lists globally configured MCPs that are not currently enabled; already enabled global MCPs are available by default and are not shown here. Selected MCPs display a checkmark, and you can use the remove icon to exclude them before creating the project.

If you select a global MCP, Ideavo opens its configuration dialog with the available details pre-filled. To include it in the new project, switch the scope toggle from **Global** to **Project**, then submit the dialog. When submitted, that MCP becomes project-only for this project and is removed from the global MCP list.

<div style="{ display: &#x22;flex&#x22;, gap: &#x22;1rem&#x22;, alignItems: &#x22;flex-start&#x22;, flexWrap: &#x22;wrap&#x22; }">
  <DocImage src="features/mcp/new-project-selector" alt="The Select MCPs popover with Neon checked under Global, more servers under Available Servers, and the add button highlighted" width="572" height="744" />

  <DocImage src="features/mcp/project-scope-toggle" alt="The Context7 configuration dialog with the Scope toggle highlighted and set to Project" width="896" height="1264" />
</div>

Changes made here apply only to the project being created.

You can also click the **+** button in the top-right of the selector to add a custom MCP for the project. Custom MCPs added during project creation are also project-specific and are not saved as global MCPs.

## Custom MCPs [#custom-mcps]

Beyond the predefined list, you can connect any MCP-compatible server to Ideavo.

### Adding a Custom MCP [#adding-a-custom-mcp]

<Steps>
  <Step>
    Click the 

    **+**

     button in the top-right of the MCP panel.
  </Step>

  <Step>
    Enter a 

    **name**

     and provide the 

    **server URL or configuration**

    .
  </Step>

  <Step>
    Select a 

    **scope**

     — Local or Global.
  </Step>

  <Step>
    Click 

    **Save**

    . The MCP is available to the agent immediately.
  </Step>
</Steps>

## Scope [#scope]

Every MCP is enabled at a specific scope. Use the **All / Local / Global** tabs at the top of the MCP panel to filter by scope.

### Local [#local]

Active only within the current project. This includes MCPs selected during project creation. Best for project-specific tools like a particular database or staging API.

### Global [#global]

Active across all your Ideavo projects. Best for general-purpose tools you use everywhere.

## Permissions [#permissions]

MCP access varies by role.

| Action                           | Owner | Admin | Editor | Viewer |
| -------------------------------- | :---: | :---: | :----: | :----: |
| View MCP panel                   |   ✓   |   ✓   |    ✓   |    —   |
| Enable / disable project MCPs    |   ✓   |   ✓   |    ✓   |    —   |
| Add / remove custom project MCPs |   ✓   |   ✓   |    ✓   |    —   |
| View owner's global MCP state    |   ✓   |   ✓   |    ✓   |    —   |
| Modify owner's global MCPs       |   ✓   |   —   |    —   |    —   |

Admins and Editors can manage project-scoped MCPs freely. They can see which of the owner's global MCPs are active, but cannot toggle or modify them. Viewers have no access to the MCP panel at all.

<Callout type="info">
  If a collaborator needs access to a specific integration, the owner should
  enable it as a **local MCP** so it is available to all Editors and above.
</Callout>

## Browser Automation with Playwright [#browser-automation-with-playwright]

Enabling the Playwright MCP gives the agent control of a real browser, unlocking:

* **Visual testing** — verify UI elements render correctly and flag regressions
* **End-to-end testing** — simulate clicks, form submissions, and navigation flows
* **Debugging** — browse your running app to catch layout issues or broken flows
* **Web research** — fetch live data from sites that require JavaScript rendering

<Callout type="warn">
  Playwright spins up a real browser in the sandbox and consumes more resources
  than standard MCPs. Disable it when not actively in use.
</Callout>

### FAQ [#faq]

<Accordions>
  <Accordion title="Why does enabling MCPs increase my token usage?">
    Each active MCP adds its tool definitions to the agent's context window, and
    MCP responses are included in the conversation. More MCPs enabled means a
    larger context and higher token consumption per message.
  </Accordion>

  <Accordion title="Can collaborators use my global MCPs?">
    Admins and Editors can see your active global MCPs but cannot modify them.
    The agent uses your global MCP connections when processing their prompts —
    usage is billed to you as the project owner.
  </Accordion>

  <Accordion title="What happens if a custom MCP server goes offline?">
    The agent will fail to reach that MCP's tools and may report an error. Other
    MCPs and the core agent continue to work normally. Update or remove the
    server URL from the MCP panel once it's back online.
  </Accordion>

  <Accordion title="Can I enable the same MCP at both local and global scope?">
    Yes — there is no conflict. Disabling it locally does not affect the global
    setting, and vice versa.
  </Accordion>
</Accordions>
