> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowra.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP in the dashboard

> Register MCP servers so agents can use their tools, and install Cursor or Claude with OAuth or an API key.

[MCP Servers](https://flowra.dev/dashboard/mcp) registers Model Context Protocol servers so their tools appear in **Select Tools** and agent configuration.

You can also expose **an agent itself** as MCP: on the agent list use **Install as MCP**, or on **Entry points** use **Use as MCP** → **Install**. That path installs the agent for Cursor, Claude, and similar clients — see [Workflows in the dashboard](/product/workflows-in-dashboard) and [Entry points and channels](/product/entry-points-and-channels).

## Connect your coding agent

Click **Connect agent** at the top of [MCP Servers](https://flowra.dev/dashboard/mcp). The same card appears once after you create a project.

* **Cursor** — click **Add to Cursor**. Cursor adds `https://mcp.flowra.dev/mcp` with no headers and opens Flowra sign-in.
* **Claude Code** — copy the `claude mcp add --transport http flowra https://mcp.flowra.dev/mcp` command.
* **Codex and others** — copy the URL or config from the matching tab.

The client sees six tools: discover, schemas, connections, run, and the JavaScript and bash sandboxes. Copy the skill command from the same dialog so the agent knows the order to call them.

## Add a server

<Steps>
  <Step title="Create MCP server">
    Open MCP, create a server, and give it a name. Choose a mode when offered:

    * **NORMAL** — tools are used as explicitly pinned selections
    * **SMART (Meta)** — broader discovery; you can constrain toolkit participation with whitelist or blacklist when the UI offers it
  </Step>

  <Step title="Load tools">
    Open **Tools** on the server row, sync the tool list, and choose which tools to expose.
  </Step>

  <Step title="Install and config">
    For most clients, skip a server ID and use the hosted endpoint `https://mcp.flowra.dev/mcp`. First request creates a default META server for the project. Pages: [Agents](https://flowra.dev/agents).

    Open **Install & Config**. Prefer **Sign in (OAuth)** for Cursor or Claude — paste the URL with no headers; the client opens Flowra sign-in and you pick a project. Use the **API key** tab for CI or clients that cannot run OAuth (`x-api-key` plus `x-username`).

    Use a *named* server (pinned NORMAL tools) when you need a fixed tool list. The same OAuth / API key choice applies to that server’s URL.
  </Step>
</Steps>

## External MCP by URL

In tool-selection modals you can sometimes load tools from an external MCP base URL (optional headers), then select tools. Those picks are stored with the agent like other MCP selections.

## Tips

* Give credentials only the access the automation needs.
* If tools do not appear, re-check server health and mode, then revisit [Toolkits and tools](/product/toolkits-and-tools).
* MCP servers are shared for the project. OAuth binds the client to the project you pick at consent. Use **x-username** (or the End user switcher when testing) so each end user keeps separate connections.
* Bind toolkit **App credentials** when the UI asks which project credentials each toolkit uses — [App credentials](/product/app-credentials).

## Developers

Deep dive on Smart vs Normal and API: [MCP](/guides/mcp). Recipe: [Use MCP in Cursor](/recipes/use-mcp-in-cursor).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.