> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/ai/mcp-server/setup.md). # Setup Connect your AI assistant to your Limio environment in a few steps. You'll sign in with your existing Limio credentials — no API keys or tokens to manage. {% hint style="warning" %} **Beta:** The Limio MCP Server is in beta and available on Release 115 onwards. If your environment is on an earlier release, contact your Limio admin about upgrading. {% endhint %} ## What you'll need * **Claude Desktop, Claude Code or Codex** (other MCP-compatible clients should also work) * **Your MCP server URL** — your Limio environment URL with `/mcp` appended (e.g., `https://your-tenant.your-domain.com/mcp`) * **Your Limio login** — the same credentials you use to sign in to Limio ## Connect via Claude Desktop Claude Desktop supports remote MCP servers as [custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). 1. Open Claude Desktop and go to **Settings > Connectors** 2. Click **Add custom connector** 3. Enter your Limio MCP server URL (e.g., `https://your-tenant.your-domain.com/mcp`) 4. Click **Add** 5. Claude will open a browser window for you to sign in with your Limio credentials. 6. Once connected, enable the Limio connector in any conversation via the **+** button in the chat input, then **Connectors**. 7. Try asking: **"Show me my Limio offers"** {% hint style="info" %} **Team and Enterprise plans:** An admin must first add the connector in **Organization settings > Connectors**. Team members can then connect from their own **Settings > Connectors** page. {% endhint %} {% hint style="info" %} **Multiple environments:** Add a separate connector for each environment (sandbox, pre-production, production). This keeps your environments isolated and lets you test workflows in sandbox before running them against production. You can name each connector to make it clear which environment it points to (e.g., "Limio Sandbox", "Limio Prod"). {% endhint %} {% hint style="info" %} **Read-only access:** When adding a connector, you can [restrict it to read-only tools](https://support.claude.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers). In Claude Desktop, go to your connector settings and disable write tools (create, update) if you only need to query data. This is a good default for production environments. {% endhint %} ## Connect to Claude Code Run the following command in your terminal: ```zsh claude mcp add --transport http limio https://your-tenant.your-domain.com/mcp ``` Replace the example URL with your environment URL. Claude Code will prompt you to authenticate through your browser on first use. You can use your existing credentials to authenticate. See the [Claude Code MCP docs](https://code.claude.com/docs/en/mcp) for more on managing MCP servers. If you want to add multiple MCP servers (for example, one for each environment, you can name each one differently to make it clear which environment they refer to). ```zsh claude mcp add --transport http limio-dev https://your-tenant-dev.your-domain.com/mcp claude mcp add --transport http limio-stg https://your-tenant-stg.your-domain.com/mcp ``` **Tip:** To make your Limio MCP server available across all projects, install it with the `--scope user` flag: ```zsh claude mcp add --scope user --transport http limio https://your-tenant-dev.your-domain.com/mcp ``` By default, Claude Code uses local scope, so the server is only available in the current project. Applying the user scope means you don't have to reinstall the server for each of your projects. Once you have Claude Code open, you can run `/mcp` to see your available MCP servers. Select the one you just added and select Authenticate. This should open up a browser with a login screen. Use your regular Limio App credentials to sign in. It should display a success message. You can then close this window and start to use the Limio MCP inside of Claude Code. ## Connect to Codex Run the following command in your terminal: ```zsh codex mcp add limio --url https://your-tenant.your-domain.com/mcp ``` Replace the example URL with your environment URL. You can then run: ```zsh codex mcp limio login ``` to initiate the authentication flow. ## Other MCP clients Any client that supports remote MCP servers can connect. Point it at your MCP server URL — the server handles authentication automatically through your browser. ## Troubleshooting | Problem | Solution | | -------------------------------- | ----------------------------------------------------------------------------- | | No hammer icon in Claude Desktop | Check that the config file is valid JSON and restart Claude Desktop | | Login page doesn't appear | Verify the MCP server URL with your Limio admin | | "Unauthorized" after login | Your Limio account may not have MCP access enabled — contact your Limio admin | If you're stuck, reach out to [Limio Support](https://docs.limio.com/support). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.limio.com/ai/mcp-server/setup.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.