Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Polytomic MCP Server trigger the 'Salesforce to Snowflake' sync"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for interacting with the Polytomic API.
Tool | Description |
| List all available connection types (connectors) |
| List all data connections |
| Get details for a specific connection |
| Create a new data connection |
| Update an existing connection |
| Delete a connection |
Tool | Description |
| List all data models |
| Get details and fields for a specific model |
| Create a new data model |
| Update an existing model |
| Delete a model |
Tool | Description |
| List all model syncs |
| Get details for a specific sync |
| Create a new model sync |
| Update an existing sync |
| Delete a sync |
| Activate (enable) a sync |
| Manually trigger a sync to run |
| Get the current status of a sync |
| List execution history for a sync |
| Get details for a specific sync execution |
Tool | Description |
| List all bulk syncs |
| Get details for a specific bulk sync |
| Create a new bulk sync |
| Update an existing bulk sync |
| Delete a bulk sync |
| Activate or deactivate a bulk sync |
| Manually trigger a bulk sync to run |
| Get the current status of a bulk sync |
| List execution history for a bulk sync |
| Get available schemas/tables for a bulk sync |
| Update which schemas/tables are enabled for a bulk sync |
Related MCP server: nango-mcp-server
Create and activate a virtual environment:
cd projects/mcp-servers/polytomic
python -m venv venv
source venv/bin/activateInstall the package:
pip install -e .Run the server:
python -m polytomic_mcp.server
# or
polytomic-mcpPOLYTOMIC_API_KEY - Your Polytomic API key (Bearer token)
The server is configured in mcporter and can be used via:
mcporter call polytomic.list_connections
mcporter call polytomic.get_sync id=<sync-id>
mcporter call polytomic.trigger_sync id=<sync-id>Activate or deactivate a bulk sync.
Args: id: The bulk sync ID active: True to activate, False to deactivate
Inputs: id (required), active. Returns: result
Activate (enable) a sync.
Args: id: The sync ID to activate
Inputs: id (required). Returns: result
Create a new bulk sync (ELT) in Polytomic.
Args: name: Name for the bulk sync source_connection_id: Source connection ID dest_connection_id: Destination connection ID destination_configuration: JSON string with destination config (e.g. {"schema": "public"}) schedule: Optional JSON for schedule source_configuration: Optional JSON string with source-specific config
Inputs: name (required), source_connection_id (required), dest_connection_id (required), destination_configuration (required), +2… Returns: result
Create a new data connection in Polytomic.
Args: name: Name for the connection type: Connection type (e.g. 'postgresql', 'salesforce', 'snowflake') configuration: JSON string with connection config (varies by type)
Inputs: name (required), type (required), configuration (required). Returns: result
Create a new data model in Polytomic.
Args: name: Name for the model connection_id: The connection ID this model uses configuration: JSON string with model config (e.g. {"query": "SELECT * FROM users"} or {"table": "users"}) identifier: Optional field name to use as unique identifier tracking_columns: Optional JSON array of column names for change tracking
Inputs: name (required), connection_id (required), configuration (required), identifier, +1 more. Returns: result
Create a new model sync (reverse ETL) in Polytomic.
Args: name: Name for the sync mode: Sync mode ('create', 'update', 'updateOrCreate', 'replace', 'append') target: JSON string with target config {"connection_id": "...", "object": "...", "configuration": {...}} fields: JSON array of field mappings [{"source": {"field": "...", "model_id": "..."}, "target": "..."}] identity: Optional JSON for identity mapping (required for update modes) schedule: Optional JSON for schedule {"frequency": "manual|hourly|daily|weekly|monthly", ...} filters: Optional JSON array of filters filter_logic: Optional filter logic string (e.g. "A AND B")
Inputs: name (required), mode (required), target (required), fields (required), +4 more. Returns: result
Delete a bulk sync from Polytomic.
Args: id: The bulk sync ID to delete
Inputs: id (required). Returns: result
Delete a connection from Polytomic.
Args: id: The connection ID to delete
Inputs: id (required). Returns: result
Delete a model from Polytomic.
Args: id: The model ID to delete
Inputs: id (required). Returns: result
Delete a sync from Polytomic.
Args: id: The sync ID to delete
Inputs: id (required). Returns: result
Get details for a specific bulk sync.
Args: id: The bulk sync ID
Inputs: id (required). Returns: result
Get available schemas/tables for a bulk sync.
Args: id: The bulk sync ID
Inputs: id (required). Returns: result
Get the current status of a bulk sync.
Args: id: The bulk sync ID
Inputs: id (required). Returns: result
Get details for a specific connection.
Args: id: The connection ID
Inputs: id (required). Returns: result
Get details and fields for a specific model.
Args: id: The model ID
Inputs: id (required). Returns: result
Get details for a specific sync.
Args: id: The sync ID
Inputs: id (required). Returns: result
Get details for a specific sync execution.
Args: sync_id: The sync ID execution_id: The execution ID
Inputs: sync_id (required), execution_id (required). Returns: result
Get the current status of a sync.
Args: id: The sync ID
Inputs: id (required). Returns: result
List execution history for a bulk sync.
Args: id: The bulk sync ID limit: Maximum number of executions to return (default 10)
Inputs: id (required), limit. Returns: result
List all bulk syncs in Polytomic.
Inputs: no named parameters. Returns: result
List all data connections in Polytomic.
Inputs: no named parameters. Returns: result
List all available connection types (connectors) in Polytomic.
Inputs: no named parameters. Returns: result
List all data models in Polytomic.
Inputs: no named parameters. Returns: result
List execution history for a sync.
Args: id: The sync ID limit: Maximum number of executions to return (default 10)
Inputs: id (required), limit. Returns: result
List all model syncs in Polytomic.
Inputs: no named parameters. Returns: result
Manually trigger a bulk sync to run.
Args: id: The bulk sync ID to trigger
Inputs: id (required). Returns: result
Manually trigger a sync to run.
Args: id: The sync ID to trigger
Inputs: id (required). Returns: result
Update an existing bulk sync in Polytomic.
Args: id: The bulk sync ID to update name: Optional new name schedule: Optional JSON for schedule destination_configuration: Optional JSON string with destination config source_configuration: Optional JSON string with source config
Inputs: id (required), name, schedule, destination_configuration, +1 more. Returns: result
Update which schemas/tables are enabled for a bulk sync.
Args: id: The bulk sync ID schemas: JSON array of schema configurations
Inputs: id (required), schemas (required). Returns: result
Update an existing connection in Polytomic.
Args: id: The connection ID to update name: Optional new name for the connection configuration: Optional JSON string with connection config
Inputs: id (required), name, configuration. Returns: result
Update an existing data model in Polytomic.
Args: id: The model ID to update name: Optional new name for the model configuration: Optional JSON string with model config (e.g. {"query": "SELECT * FROM users"}) identifier: Optional field name to use as unique identifier tracking_columns: Optional JSON array of column names for change tracking
Inputs: id (required), name, configuration, identifier, +1 more. Returns: result
Update an existing sync in Polytomic.
Args: id: The sync ID to update name: Optional new name mode: Optional sync mode fields: Optional JSON array of field mappings identity: Optional JSON for identity mapping schedule: Optional JSON for schedule filters: Optional JSON array of filters filter_logic: Optional filter logic string active: Optional boolean to enable/disable sync
Inputs: id (required), name, mode, fields, +5 more. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 32 tools
Tools are well-organized around distinct resources (bulk syncs, syncs, connections, models) with clear action differentiation. Minor overlap exists between 'activate_sync' and 'update_sync' with active parameter, but descriptions clarify their distinct purposes (activation vs. full update).
Perfectly consistent verb_noun pattern throughout (e.g., create_bulk_sync, get_connection, list_models). All tools use snake_case with clear action prefixes (create, get, list, update, delete, activate, trigger) followed by resource names.
32 tools is borderline heavy for a data integration server, though it covers multiple resource types comprehensively. The count feels slightly inflated due to parallel tools for bulk syncs and syncs, but remains manageable given the domain complexity.
Excellent CRUD/lifecycle coverage for all core resources (connections, models, bulk syncs, syncs). Includes activation, triggering, status checks, execution history, and schema management. No apparent gaps for the data integration domain.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Authenticated MCP server for ClearPolicy policy and compliance workflows.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
