MCPs are available on all paid plans.
What are MCPs?
MCPs let you attach third-party MCP servers (Slack, HubSpot, Stripe, Grafana, PostgreSQL, Supabase, custom internal servers, and more) to your Nekt workspace. Once attached, their tools are exposed through the Nekt MCP Gateway together with your catalog data, Context Layer, and context documents. Your agent connects to a single endpoint (your Nekt MCP Gateway) and gets:- Nekt’s own tools for querying tables, running Queries and Notebooks, and reading context documents.
- Tools from every MCP you’ve attached, discovered and invoked through the same dispatcher.
Attach an MCP
1
Open the MCPs module
Go to Activate → MCPs in the sidebar and click + New MCP.
2
Pick a connector
Choose from the list of supported MCP integrations. Custom MCP servers can also be added by URL. See MCP connectors for each connector’s setup steps and tools.
3
Name it and add a description
Give the MCP a short name and a description explaining what it’s used for. Descriptions are read by the agent to help it choose between MCPs of the same type (for example, “Slack for marketing” vs “Slack for engineering”).
4
Authenticate
Connect to the MCP server using its native auth flow. OAuth for most SaaS connectors, API key or connection string for databases. If someone else holds the account, share a setup link with them instead.
5
Select tools
Pick which tools from the MCP your agent will be allowed to use. Each tool is annotated as Read or Write so you can enable them intentionally.
6
Set access
On Growth and Custom plans, choose which users and groups in your workspace can use this MCP through the Gateway. See Access levels.
How the agent uses attached MCPs
Tools from your MCPs are not listed individually to the agent. Instead, the Nekt MCP Gateway exposes two dispatcher tools that cover all of them:discover_live_toolsreturns the attached MCPs, their tools, and the input schemas.run_live_toolinvokes a specific tool with arguments.
get_semantic_context first to decide whether a question should be answered from warehoused data or routed to a live tool. After a successful routing, it can save a context document so the next similar question goes to the right place automatically.
MCP connectors
Every MCP connector Nekt supports has its own page under MCPs → Connectors in the sidebar, with how to set up its access and the full list of the tools it exposes, each marked Read or Write. A connector’s page is updated every time a new version of it is released, including what changed.Attach an MCP over the API
Everything above is also available through the Platform API, which is what you want when each of your own clients brings their own credentials: create one connection per client, send each of them a setup link, and let a callback webhook tell you when they are done. See Connect an MCP with a setup link for the full flow.Managing MCPs
From the MCPs list you can:- Enable or disable an MCP without deleting it.
- Tag MCPs to group them by team, purpose, or environment.
- Edit permissions to change who can use it.
- Update the tool selection as the underlying MCP server adds or removes tools.
Access levels
On Growth and Custom plans, access is per connection:
The person who creates an MCP becomes its Manager. A Viewer or Editor grant can be limited to a subset of the MCP’s tools. On other paid plans, access is not restricted per connection.
API & MCP
Platform API
List, create, and manage MCP connections and their tools.
MCP tools
discover_live_tools and run_live_tool reach your connected apps.Related
Nekt MCP Gateway
The endpoint your agent connects to.
Live Data tools
How attached MCPs surface to agents technically.
Context Layer
Context documents that steer routing.
MCP Server setup
Enable the Gateway on Express, GCP, or AWS.
Connect an MCP over the API
Setup links and callback webhooks, one connection per client.
MCP connectors
Every supported connector, with its setup steps and tools.