Setup
Connect your AI assistant to your Limio environment in a few steps. You'll sign in with your existing Limio credentials. There are no API keys or tokens to manage.
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.
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
/mcpappended, for examplehttps://your-tenant.your-domain.com/mcpYour 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.
Open Claude Desktop and go to Settings > Connectors
Click Add custom connector
Enter your Limio MCP server URL (e.g.,
https://your-tenant.your-domain.com/mcp)Click Add
Claude will open a browser window for you to sign in with your Limio credentials.
Once connected, enable the Limio connector in any conversation via the + button in the chat input, then Connectors.
Try asking: "Show me my Limio offers"
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.
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").
Read-only access: When adding a connector, you can restrict it to read-only tools. 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.
Connect to Claude Code
Run the following command in your terminal:
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 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).
Tip: To make your Limio MCP server available across all projects, install it with the --scope user flag:
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:
Replace the example URL with your environment URL. You can then run:
to initiate the authentication flow.
Connect to Microsoft 365 Copilot
This connection is only available via Federated MCP connector and required one of the following Microsoft addons:
Researcher agent
Deep research mode in Copilot Chat
Copilot in Excel
This is typically found in the Microsoft 365 Copilot Business plan.
You will require some configuration details from Limio for the below setup so it is recommend to raise a ticket with Support requesting details for Microsoft 365 Copilot setup for the environment you're targeting.
Register the OAuth connection
Navigate to https://dev.teams.microsoft.com -> Tools -> OAuth Client Registration
Click + Register client and enter:
Registration name
Limio MCP <ENVIRONMENT>
Base URL
https://<LIMIO_APP_URL>/mcp
Restrict usage by organization
My organization only
Restrict usage by Teams app
Select your relevant option
Client ID
Use client_id provided in support request
Client Secret
Use client_secret provided in support request
Authorization endpoint
Use authorization_endpoint provided in support request
Token endpoint
Use token_endpint provided in support request
Refresh endpoint
Use refresh_endpoint provided in support request
Scope
Copy and paste the value in scopes provided in the support request.
Enable Proof Key for Code Exchange
Enabled
Client password authentication method
HTTP Basic authentication
Click Save
Copy and note down the OAuth client registration ID
Configure MCP in M365 admin console
Navigate to the Connectors (Admin home page -> Copilot -> Connectors) section.
Click + Add Connection and select Created by your org from the Categories sections in the left.
Click Add within the Create a new connector box.
Click Add within the Connect to MCP server box.
Display Name
Limio MCP <ENVIRONMENT>
MCP endpoint URL
https://<LIMIO_APP_URL>/mcp
Authentication type
OAuth 2.0
Reference ID
Use OAuth client registration ID from earlier
Click Authorize.
You will be present with login screen, use your Limio credentials to log in.
Tick the Notice box and fianlly click Create.
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
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.
Last updated
Was this helpful?