Skip to main content
The Planasonix MCP server lets you manage pipelines, create connections, set schedules, and troubleshoot failures through natural language conversations with AI assistants. It uses the open Model Context Protocol and works with any compatible client.

22 tools

Pipeline operations, schedule management, and connection configuration.

AI pipeline creation

Describe what you want and the backend AI builds the graph.

Full tenant isolation

Every request is scoped to your organization. Cross-org access is impossible.

Prerequisites

  • A Planasonix account (Professional plan or above)
  • An AI client that supports MCP (Claude Desktop, Cursor, Windsurf, VS Code, or similar)
  • A Planasonix API key with the required scopes

Generate your API key

1

Open API keys

Go to Settings → API Keys in your Planasonix dashboard.
2

Create a key

Click Generate New Key and select the scopes you need.
3

Copy the key

Copy the full key immediately — it is only shown once.

Available scopes

ScopeGrants
pipelines:readView pipelines, run history, health metrics
pipelines:writeCreate, modify, trigger, pause, resume, delete pipelines
connectors:readView and test connectors
connections:readView connections and connection types
connections:writeCreate, update, delete connections
schedules:readView pipeline schedules
schedules:writeCreate, update, enable, disable, delete schedules
Keep your API key secure. It grants access to your organization’s pipeline data. Do not share it or commit it to source control.

Download and install

Download the latest binary from GitHub Releases or from Settings → MCP Server in your dashboard.
PlatformFile
macOS (Apple Silicon)planasonix-mcp-darwin-arm64
macOS (Intel)planasonix-mcp-darwin-amd64
Linux (x86_64)planasonix-mcp-linux-amd64
Linux (ARM)planasonix-mcp-linux-arm64
Windowsplanasonix-mcp-windows-amd64.exe
chmod +x planasonix-mcp-darwin-arm64
sudo mv planasonix-mcp-darwin-arm64 /usr/local/bin/planasonix-mcp
On macOS, if you see a quarantine warning, run: xattr -d com.apple.quarantine /usr/local/bin/planasonix-mcp

Configure your AI client

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
  "mcpServers": {
    "planasonix": {
      "command": "/usr/local/bin/planasonix-mcp",
      "args": ["--stdio"],
      "env": {
        "PLANASONIX_API_KEY": "flx_your_key_here",
        "PLANASONIX_API_URL": "https://api.planasonix.com"
      }
    }
  }
}
Restart Claude Desktop. A hammer icon confirms MCP tools are active.
Windows users: replace /usr/local/bin/planasonix-mcp with the full path to the .exe, for example C:\\Program Files\\Planasonix\\planasonix-mcp.exe.

Verify the connection

After restarting your AI client, type:
List my Planasonix pipelines
If you see pipeline data, the MCP server is connected.

Available tools

Pipeline operations

ToolScopeWhat it does
list_pipelinespipelines:readList all pipelines with status and schedule
get_pipelinepipelines:readGet details for a specific pipeline
get_run_historypipelines:readView recent run history with error details
get_pipeline_healthpipelines:readError rate, latency, rows processed, SLA status
trigger_pipelinepipelines:writeTrigger an immediate pipeline run
pause_pipelinepipelines:writePause a pipeline’s schedule
resume_pipelinepipelines:writeResume a paused pipeline
create_pipelinepipelines:writeCreate a pipeline from a natural language description
update_pipelinepipelines:writeModify a pipeline using natural language
delete_pipelinepipelines:writeSoft-delete a pipeline (recoverable from UI)

Schedule management

ToolScopeWhat it does
list_schedulesschedules:readList all pipeline schedules
create_scheduleschedules:writeCreate a cron-based schedule for a pipeline
update_scheduleschedules:writeUpdate a schedule’s cron, frequency, or timezone
delete_scheduleschedules:writePermanently delete a schedule
enable_scheduleschedules:writeRe-enable a disabled schedule
disable_scheduleschedules:writeDisable a schedule without deleting it

Connection management

ToolScopeWhat it does
list_connectorsconnectors:readList configured source/destination connectors
test_connectionconnectors:readTest connector reachability and latency
list_connection_typesconnections:readDiscover available connector types
create_connectionconnections:writeCreate a new data source or destination
update_connectionconnections:writeUpdate a connection’s name or parameters
delete_connectionconnections:writeDelete a saved connection

AI-powered pipeline creation

The create_pipeline and update_pipeline tools use backend AI to generate pipeline graphs from natural language. Creating a pipeline:
Create a pipeline called "Daily Orders Sync" that extracts orders from
PostgreSQL, filters to the last 7 days, deduplicates by order_id,
and loads into Snowflake.
The AI generates the complete pipeline with source, transform, and destination nodes. Modifying a pipeline:
Add a step to the Daily Orders Sync pipeline that converts order_date
from UTC to EST before loading into Snowflake.
The AI determines which nodes and edges to add while preserving the existing structure.
AI-powered operations can take up to 2 minutes for complex descriptions. The MCP server uses a 120-second timeout for these requests.

Security and data isolation

The MCP server enforces full tenant isolation. Every request is scoped to your organization based on the API key — client-supplied parameters can never override the server-side identity.
  • Scope-based access control — read-only keys cannot trigger or modify pipelines
  • Revocable — keys can be revoked at any time from Settings → API Keys
  • Audit trail — all MCP requests are logged
  • No data passthrough — the MCP server is a control plane proxy; pipeline data flows directly between sources and destinations
  • Rate limited — 60 req/min (Professional), 120 req/min (Premium), 300 req/min (Enterprise)

Enterprise: remote deployment

For organizations whose security policies prohibit local binary execution, the MCP server supports a remote HTTP+SSE transport:
{
  "mcpServers": {
    "planasonix": {
      "type": "url",
      "url": "https://mcp.planasonix.com/sse",
      "headers": {
        "Authorization": "Bearer flx_your_key_here"
      }
    }
  }
}
Self-hosted Docker deployment is also available:
docker run -d \
  --name planasonix-mcp \
  -p 8080:8080 \
  -e PLANASONIX_API_URL=https://your-instance.planasonix.com \
  -e DATABASE_URL=postgres://user:pass@db:5432/planasonix \
  planasonix/mcp-server:latest

Troubleshooting

ProblemSolution
AI client doesn’t show MCP toolsVerify config JSON is valid. Check binary path is correct and executable.
”Unauthorized” errorAPI key may be invalid or revoked. Generate a new one in Settings → API Keys.
”Insufficient permissions” errorKey is missing the required scope. Generate a new key with the right scopes.
Pipeline creation times outAI generation can take up to 2 min. Simplify the description or break into steps.
macOS quarantine warningRun: xattr -d com.apple.quarantine /usr/local/bin/planasonix-mcp

API keys

Create and manage API keys for Planasonix.

Orchestration

Schedules, triggers, and pipeline chaining.

Connections

Configure data sources and destinations.

GitHub repository

Source code and release downloads.