Skip to main content
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, Semantic 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.
This lets the agent reason across your warehoused data and your live systems in one conversation, using the context documents in your Semantic Layer to route each question to the right place.

​
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.
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.
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

Choose which users and groups in your workspace can use this MCP through the Gateway.

​
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: The agent typically calls 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.
Write-capable tools require explicit confirmation from the agent before each call.

​
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.

Nekt MCP Gateway

The endpoint your agent connects to.

Live Data tools

How attached MCPs surface to agents technically.

Semantic Layer

Context documents that steer routing.

MCP Server setup

Enable the Gateway on Express, GCP, or AWS.