Custom MCP servers

What custom MCPs unlock

Kognita's built-in integrations cover codebase intelligence, Jira, and database access. Custom MCPs extend the same managed agent runtime to any MCP server your team approves. This matters for developers and for customers: the same assistant can understand the code, explain the system, and reach the connected tools that surround it.

• Connect the Kognita managed project agent to approved external MCP servers, not only Kognita built-ins.
• Bring internal tools, business systems, databases, ticketing systems, and automation platforms into the same agent runtime as your codebase context.
• Use a hosted third-party MCP endpoint or host your own public HTTPS MCP server when your team wants to expose internal workflows safely.
• Use Zapier MCP to expose approved app actions from Gmail, Slack, Google Calendar, Salesforce, HubSpot, Notion, Jira, and thousands of other apps.
• Give product, support, operations, and management a single place to ask codebase questions and, when approved, reach connected systems.
• Keep the agent grounded with explicit guidance that explains what each custom MCP does and when it should be used.

How it works in Kognita

Network allowlist for self-hosted MCPs

If you host your own MCP server behind a firewall, reverse proxy, API gateway, or cloud security group, allow inbound HTTPS traffic from the same Kognita egress IP shown in the dashboard database setup: 35.254.19.175.

Kognita custom MCP URLs must still be public HTTPS endpoints. The allowlist is for teams that expose a controlled endpoint publicly but restrict which source IPs can reach it.

Zapier MCP example

Zapier documents MCP support for 8,000+ app connections and 30,000+ actions. In Kognita, that means a project agent can keep using semantic codebase context while also reaching approved Zapier tools, such as calendar lookup, Slack updates, CRM records, spreadsheet rows, or ticket actions.

01

Create a Zapier MCP server

Open Zapier MCP, click New MCP Server, and choose the MCP client type. For Kognita, choose Other so Zapier gives you a generic MCP server URL that can be pasted into a custom MCP connection.

02

Add the app you want the agent to use

In the Zapier MCP Apps tab, add a tool and search for the app you want. This example searches for calendar tools and selects Google Calendar.

03

Choose exact tools and permissions

Select only the tools the Kognita agent should be able to use. You can add all available tools, only search tools, only action tools, or specific actions one by one.

04

Connect the app account

Choose the app account Zapier should use, then add the selected tools to the MCP server. The Kognita agent will only see the Zapier tools you configured for this server.

05

Copy the Zapier MCP server URL

Open the Connect tab in Zapier MCP and copy the server URL. Treat this URL like a secret because it authorizes access to the tools configured on that Zapier MCP server.

06

Add Zapier as a custom MCP in Kognita

In your Kognita project, open MCPs, click Add MCP server, choose Streamable HTTP, paste the Zapier server URL, and add clear agent guidance such as what the calendar tools are for.

07

Refresh the environment and use the tools

After saving the custom MCP, refresh the project agent environment. The assistant can then use the configured external tools alongside Kognita semantic code intelligence, Jira, and database context.

Security notes

• Only connect MCP servers you trust and that your organization has approved.
• Use the smallest useful Zapier tool set instead of exposing every available action by default.
• Treat external MCP URLs and tokens as secrets because they can grant access to configured external actions.
• Use least-privilege external app accounts and rotate credentials when access changes.
• Keep agent guidance specific so the agent knows the intended scope of each custom MCP server.

FAQ

Next steps