What are MCP connectors?
MCP connectors link external MCP servers — such as Jira, Notion, GitHub, or your own internal tools — to your NextKS organization. Once connected, the tools they expose become available in two places:- Chat bot — Team members can use the tools by chatting with the NextKS bot in Slack or Teams
- NextKS MCP — Tools like Claude Desktop, Claude Code, and Cursor can access them through the NextKS MCP endpoint
Organization connectors
Created by admins. Available to every member of the organization. Managed from Admin → MCP Connectors.
Personal connectors
Created by individual users. Visible only to the user who created them. Managed from MCP Connectors in the sidebar.
Adding a connector
- Organization connector (admin)
- Personal connector
- Go to Admin → MCP Connectors in the sidebar
- Click Add Connector
- Fill in the connector details (see Connector settings below)
- Click Save
Organization connectors appear as read-only cards on every member’s MCP Connectors page. Only admins can create, edit, or delete them.
Connector settings
When creating or editing a connector, you configure the following fields:Name
A display name for the connector (e.g., “Jira”, “Internal Docs API”). Only letters, numbers, hyphens, underscores, and spaces are allowed. The name is automatically converted to a lowercase namespace used to prefix tool names. For example, a connector named “My Jira Server” produces the namespacemy_jira_server, and its tools appear as my_jira_server_create_issue, my_jira_server_search, etc.
URL
The HTTP(S) endpoint of the MCP server. NextKS connects to this URL to discover tools and forward tool calls at runtime.API Key
An optional authentication key sent to the MCP server with every request. The key is encrypted at rest using AES-256-GCM and is never exposed in the dashboard after saving. When editing a connector, leave this field blank to keep the existing key.AI Usage Notes
Optional free-text guidance (up to 1,000 characters) that tells the AI how and when to use this connector’s tools. These notes are included in the tool description that the AI model sees, so they directly influence how the model decides to use the tools. Good usage notes can significantly improve the AI’s behavior. For example:- “Use this connector for project management queries. Always confirm with the user before creating or modifying issues.”
- “This is the company HR system. Only use it when the user explicitly asks about HR topics like leave balances or org charts.”
- “When searching, prefer short keyword queries over long sentences. Always include the project key.”
Require tool approval
A toggle that controls whether tool calls need explicit user approval before execution. Enabled by default. When enabled, the chat bot and the NextKS MCP will ask the user to approve each tool call before it runs. This is recommended for connectors that modify data or perform sensitive actions. When disabled, tools are called automatically without approval.Enabling and disabling connectors
Each connector has an enable/disable toggle on its card. When you disable a connector, its tools are immediately removed from both the chat bot and the NextKS MCP. No data is lost — you can re-enable it at any time. When re-enabling, NextKS tests the connection first. If the MCP server is unreachable, the connector stays disabled and shows an error.Health monitoring
NextKS automatically monitors the health of all enabled connectors:- Automatic pings — Every 5 minutes, NextKS pings each enabled connector to check if it’s responding. The result is reflected in the status badge on the connector card.
- Auto-refresh — The connectors page polls for status changes every 30 seconds, so you see updates without refreshing the page.
Status badges
| Badge | Meaning |
|---|---|
| Connected (green) | The connector is enabled and the MCP server is responding |
| Disconnected (gray) | The connector has been manually disabled |
| Error (red) | The last connection test failed (e.g., authentication error) |
| Unreachable (red) | The connector is enabled but the MCP server is not responding to health checks |
Tool discovery and caching
When a connector is created or re-enabled, NextKS connects to the MCP server and discovers all available tools. These tools are cached so they can be listed instantly in the chat bot and the NextKS MCP without reconnecting each time. Tool caches are refreshed automatically:- On every successful connection test (manual or automatic)
- During the daily maintenance cycle (every 24 hours)
Deleting a connector
Click the delete button on a connector card. You’ll be asked to confirm before the connector and its cached tool data are permanently removed.Organization vs. personal connectors
| Organization | Personal | |
|---|---|---|
| Who can create | Admins only | Any member |
| Who can see | All members | Only the creator |
| Who can edit/delete | Admins only | Only the creator |
| Managed from | Admin → MCP Connectors | MCP Connectors |
| Available in chat bot | Yes, to all members | Yes, to the creator only |
| Available in NextKS MCP | Yes, to all members | Yes, to the creator only |
| Audit logged | Yes | No |