Polytomic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POLYTOMIC_API_KEY | Yes | Your Polytomic API key (Bearer token) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connection_typesB | List all available connection types (connectors) in Polytomic. |
| list_connectionsB | List all data connections in Polytomic. |
| get_connectionC | Get details for a specific connection. Args: id: The connection ID |
| create_connectionC | 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) |
| update_connectionC | 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 |
| delete_connectionB | Delete a connection from Polytomic. Args: id: The connection ID to delete |
| list_modelsB | List all data models in Polytomic. |
| get_modelB | Get details and fields for a specific model. Args: id: The model ID |
| create_modelB | 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 |
| update_modelB | 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 |
| delete_modelB | Delete a model from Polytomic. Args: id: The model ID to delete |
| list_syncsB | List all model syncs in Polytomic. |
| get_syncC | Get details for a specific sync. Args: id: The sync ID |
| create_syncB | 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") |
| update_syncC | 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 |
| delete_syncC | Delete a sync from Polytomic. Args: id: The sync ID to delete |
| activate_syncC | Activate (enable) a sync. Args: id: The sync ID to activate |
| trigger_syncB | Manually trigger a sync to run. Args: id: The sync ID to trigger |
| get_sync_statusB | Get the current status of a sync. Args: id: The sync ID |
| list_sync_executionsC | List execution history for a sync. Args: id: The sync ID limit: Maximum number of executions to return (default 10) |
| get_sync_executionB | Get details for a specific sync execution. Args: sync_id: The sync ID execution_id: The execution ID |
| list_bulk_syncsB | List all bulk syncs in Polytomic. |
| get_bulk_syncC | Get details for a specific bulk sync. Args: id: The bulk sync ID |
| create_bulk_syncB | 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 |
| update_bulk_syncC | 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 |
| delete_bulk_syncB | Delete a bulk sync from Polytomic. Args: id: The bulk sync ID to delete |
| activate_bulk_syncB | Activate or deactivate a bulk sync. Args: id: The bulk sync ID active: True to activate, False to deactivate |
| trigger_bulk_syncC | Manually trigger a bulk sync to run. Args: id: The bulk sync ID to trigger |
| get_bulk_sync_statusB | Get the current status of a bulk sync. Args: id: The bulk sync ID |
| list_bulk_sync_executionsB | List execution history for a bulk sync. Args: id: The bulk sync ID limit: Maximum number of executions to return (default 10) |
| get_bulk_sync_schemasB | Get available schemas/tables for a bulk sync. Args: id: The bulk sync ID |
| update_bulk_sync_schemasC | Update which schemas/tables are enabled for a bulk sync. Args: id: The bulk sync ID schemas: JSON array of schema configurations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.