Skip to Content
IntegrationsCustom Integrations (MCP)

Custom Integrations (MCP)

MCP servers let you extend your assistant with custom tools beyond the built-in integrations. If you need to connect to a service that Town doesn’t support natively, MCP is the way to do it.

What is MCP?

MCP (Model Context Protocol) is a standard for connecting AI assistants to external tools and services. Think of it as a way to give your assistant access to any tool or service, even ones not built into Town.

How it works

  1. You set up an MCP server (or use one that’s already running)
  2. You add the server in Town’s settings
  3. When creating a workflow, you enable the MCP server
  4. Your assistant can now use the custom tools from that server

Setting up an MCP server

Add a server

  1. Go to Settings, then MCP
  2. Click Add Server
  3. Enter the server details:
    • Name — A display name you’ll recognize
    • URL — The server’s address
    • Description — What this server provides

Enable for a workflow

When creating or editing a workflow:

  1. Scroll to the MCP Servers section
  2. Check the servers you want to enable
  3. The workflow now has access to the custom tools

Using custom tools

Once enabled, custom tools from your MCP server work just like any other tool:

  • They appear in the workflow’s tool list
  • Your assistant uses them when appropriate
  • Results show up in the run history

Example use cases

Internal company services

Connect to your organization’s internal tools:

  • Query your internal CRM or helpdesk
  • Update ticket systems
  • Access internal databases

Specialized platforms

Integrate with industry-specific services:

  • Specialized SaaS tools
  • Industry platforms
  • Proprietary systems

Custom capabilities

Add specialized functionality:

  • Custom data processing
  • Specialized search across your data
  • Domain-specific analysis

What you’ll see

When you enable an MCP server for a workflow, the settings show:

  • Server name — Which server is connected
  • Summary — What the server provides
  • Tool count — How many tools are available
  • Impact — How much context the server adds

Only enable MCP servers that a workflow actually needs. Each server adds to the workflow’s context, which can affect performance.

Best practices

Test your MCP connection first. Before enabling for important workflows, verify that the server is accessible and responding correctly.

Monitor for issues. Check the run history to make sure custom tool calls are succeeding.

Keep it focused. Only enable the MCP servers a workflow needs. More servers means more complexity.

Learn more

Last updated on
LinearNotion