What is the Peliqan MCP Server?
The Peliqan MCP (Model Context Protocol) Server lets AI assistants like Claude.ai, Claude Code, Claude Desktop and ChatGPT talk directly to your Peliqan account. Once connected, the AI can explore your data, debug pipelines, write and run data apps, manage query tables, and call API endpoints — all without leaving your chat. Think of it as giving Claude (or any other MCP Client) a direct line into Peliqan.
Prerequisites
- A Peliqan account
- EU: use
mcp.eu.peliqan.io - US: use
mcp.us.peliqan.io - A Peliqan user (login)
- An account on e.g. Claude.ai or ChatGPT, or Claude Code or Claude Desktop installed (or any other MCP Client)
Setup
Setup in ChatGPT
Setup in Claude.ai (web) in your Personal account
Setup in Claude.ai (web) in your Organization account
Setup in Claude Code (terminal)
Setup in Claude Desktop
Setup in Copilot in Visual Studio (VS Code)
Setup in other MCP Clients
Verifying the connection
Once connected, try these prompts to confirm everything is working:
"List my Peliqan connections" "Show me all databases in my Peliqan account” "List my data apps"
If you see results from your Peliqan account, you're all set.
What the Peliqan MCP Server can do
Debug connections & pipelines
- See all your data source connections and their sync status
- View recent pipeline run history
- Read raw error logs when a sync fails
Explore your data
- Browse all databases, schemas, and tables
- Inspect column names and types
- Preview rows of data
Manage query tables
- View run history and error logs for a failing query table
- Check upstream/downstream dependencies before making changes
- Create, update, and delete SQL query tables
- Test fixes in an isolated schema before applying to production
Build & run data apps
- Write Python scripts and run them as background jobs (shell mode)
- Create interactive Streamlit web UIs and publish them with a shareable URL
- Build HTTP API handlers and expose them as REST endpoints
- Schedule scripts to run automatically
Manage API endpoints
- Create, update, and delete HTTP endpoints backed by your Python scripts
- View recent call logs for any endpoint
Sub-account management (partner accounts only)
- List all customer sub-accounts
- Run any tool against a specific sub-account by passing
sub_account_id
Resources the AI can read
Resource URI | What it contains |
peliqan://guide | Full agent guide with all use cases and workflows |
peliqan://docs/data-app-pq | Complete pq function reference + data-app examples + built-in templates |
peliqan://templates | List of all built-in script templates |
peliqan://templates/{id} | Full source code for a specific template |
These are automatically available to the AI — no extra setup needed.
Example prompts to get started
Tips
- The AI reads docs automatically — before writing any Data Apps (Python scripts), tell the AI to read
peliqan://docs/data-app-pqfirst. This ensures it uses the correctpqfunctions and script structure. - Deletions are permanent — deleting a schema, table, or data app via the MCP cannot be undone.
Need help?
Reach out to Peliqan support: support@peliqan.io. You can also ask your AI (e.g. Claude) directly. Once the Peliqan MCP Server is connected, the AI has full context on how Peliqan works.