MCP (Model Context Protocol)

MCP (Model Context Protocol)

The Model Context Protocol (MCP) is an open standard for connecting AI models to tools and data sources. ThinkFleet implements MCP both as a client (consuming external MCP servers) and as a server (exposing your tools to external MCP clients).

What is MCP?

MCP provides a standardized way for AI agents to:

• Discover available tools and their schemas
• Call tools with structured parameters
• Receive structured results

Think of it as a universal adapter between AI models and the tools they use. Instead of each AI platform implementing custom integrations, MCP provides one protocol that works everywhere.

ThinkFleet as MCP Client

Connect external MCP servers to give your agents access to additional tools.

Adding an External MCP Server

1. Navigate to MCP in the sidebar
2. Go to the Services tab
3. Click Add Server
4. Configure the server:

Field	Description
Name	Display name for the server
URL	The MCP server endpoint URL
Authentication	API key, Bearer token, or none

5. Click Save — ThinkFleet discovers available tools from the server
6. Toggle Enabled to make tools available to your agents

Featured MCP Server Templates

ThinkFleet includes pre-configured templates for popular MCP servers:

Playwright MCP

Browser automation tools for web interaction:

Tool	Description
navigate	Navigate to a URL
click	Click an element
fill	Fill in a form field
screenshot	Take a screenshot
evaluate	Execute JavaScript in the browser

File System MCP

Read and write files on a configured directory:

Tool	Description
read_file	Read file contents
write_file	Write content to a file
list_directory	List files in a directory
search_files	Search for files by pattern

Managing External Servers

From the Services tab, you can:

• Enable/Disable servers without deleting them
• Edit server configuration (URL, auth)
• Delete servers you no longer need
• View tools exposed by each server

Built-in MCP Services

ThinkFleet includes built-in MCP services that provide common tool capabilities without requiring external servers. These run as direct API calls within ThinkFleet, resulting in lower latency (~50ms vs ~200ms for flow-based tools).

Available Built-in Services

Email Service

Provider-agnostic email operations that work with Gmail and Outlook.

Tool	Parameters	Description
email_search	query, from, to, dateRange	Search emails
email_get	messageId	Get full email content
email_send	to, subject, body, cc, bcc	Send a new email
email_reply	messageId, body	Reply to an email thread

Web Scraping Service

Tool	Parameters	Description
web_scrape	url, selector	Fetch and extract web page content
web_search	query, maxResults	Search the web

Database Service

Tool	Parameters	Description
db_query	sql	Execute a read-only SQL query
db_list_tables	—	List available tables
db_describe_table	tableName	Get table schema

Translation Service

Tool	Parameters	Description
translate	text, sourceLang, targetLang	Translate text between languages

Provider Abstraction

Built-in services use a provider abstraction layer. For example, the Email service has separate providers for Gmail (using the Gmail API) and Outlook (using Microsoft Graph API). ThinkFleet automatically routes to the correct provider based on the connected account.

This means your agents and system prompts don't need to know which email provider a user has — they just use email_send and it works.

ThinkFleet as MCP Server

ThinkFleet exposes your configured tools as an MCP server, allowing external MCP clients to use them.

MCP Server Endpoint

https://your-instance.thinkfleet.com/api/v1/projects/{projectId}/mcp-server/http

Authentication

Authenticate to the MCP server using the MCP token:

curl -X POST \
  https://your-instance.thinkfleet.com/api/v1/projects/{projectId}/mcp-server/http \
  -H "Authorization: Bearer {mcpToken}" \
  -H "Content-Type: application/json" \
  -d '{"method": "tools/list"}'

Token Management

• View token: Navigate to MCP > Overview to see your MCP token
• Rotate token: Click Rotate Token to generate a new token (invalidates the old one)

Exposed Tools

The MCP server exposes all tools configured in your project:

• Flow tools — Published flows with their trigger schemas
• Piece tools — Individual piece actions you've enabled
• Built-in services — Email, web scraping, database, etc.

Skills Files

ThinkFleet generates machine-readable skill definitions:

Claude Skills Format

GET /api/v1/projects/{projectId}/mcp-server/skills.json

Returns tools in the Claude tool_use format.

OpenAPI Format

GET /api/v1/projects/{projectId}/mcp-server/skills.openapi.yaml

Returns tools as an OpenAPI 3.0 specification.

Per-Tool Skills

GET /api/v1/projects/{projectId}/mcp-server/piece-tools/{toolId}/skill.json
GET /api/v1/projects/{projectId}/mcp-server/flows/{flowId}/skill.json

Connecting External Clients

Claude Desktop

Add to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "thinkfleet": {
      "url": "https://your-instance.thinkfleet.com/api/v1/projects/{projectId}/mcp-server/http",
      "headers": {
        "Authorization": "Bearer {mcpToken}"
      }
    }
  }
}

Other MCP Clients

Any MCP-compatible client can connect using the server endpoint and token. Refer to the client's documentation for configuration details.

The MCP Page

The MCP page in ThinkFleet provides a centralized view of all MCP-related configuration:

Tabs

Tab	Description
Overview	MCP server status, token, endpoint URL
Flows	Flows exposed as MCP tools
Pieces	Piece actions exposed as MCP tools
Services	External MCP servers and built-in services
Skills	Generated skill files and links

Pieces Tab

The Pieces tab provides a two-panel browser:

• Left panel: Grid of all available pieces with search
• Right panel: Active tools grouped by piece

To add piece tools:

1. Click on a piece in the left panel
2. Click Add All to add every action, or select individual ones
3. Configure a connection for the piece
4. Tools appear in the right panel and become available to agents

Best Practices

1. Start with built-in services — They're faster and require less configuration
2. Use piece tools for specific needs — Add individual actions rather than entire pieces
3. Secure your MCP token — Treat it like an API key. Rotate it if compromised.
4. Monitor tool usage — Check which tools are being called and how often
5. Test external servers — Verify connectivity before assigning them to agents

Next Steps

• Configure agent tools
• Self-host ThinkFleet
• API reference