A central hub that lets Claude call multiple external MCP services through a single connection while preserving per-user OAuth identity. It handles service discovery by capability, orchestrates multi-service workflows with variable passing, and validates tokens via JWKS with per-service audience scoping so leaked credentials can't be replayed. Ships with connectors for Snowflake (External OAuth), Alpha Vantage, browser automation, and notifications. Also includes delivery management primitives for POVs, phases, and tasks you can query in natural language. Reach for this when you need Claude to chain operations across services that would normally require separate MCP connections, or when building workflows that must run as the authenticated user rather than a shared service account.
pAIchart is an MCP hub for AI-native delivery management — POVs, tasks, and phases you drive in natural language — plus a registry of external MCP services you can discover, call, and orchestrate into multi-service workflows.
Anyone can self-register a service; agents and AI clients then reach all of them through a single Hub with trust-level authentication and per-user OAuth passthrough.
pAIchart is a hosted MCP hub — nothing to install. Point your AI client at the endpoint, authenticate, and start asking in natural language.
https://paichart.app/mcp/prompt list to see every guided workflowOnce you're connected, try:
energy_operations_optimizer" — correlates weather forecasts with energy data into operational recommendations, a multi-service workflow across two live servicesEvery request is either answered directly or composed into a workflow across services — and every external call runs as you, never as a shared platform account:
You (Claude Desktop / ChatGPT)
→ authenticate to the pAIchart Hub
→ ask in natural language, e.g.
• "Which of my POVs are at risk?" → project / analytics tools answer directly
• "Texas energy mix + this week's weather" → Hub composes a multi-service workflow
→ for external service calls:
→ Hub discovers services by capability, determines trust level, mints a per-service JWT
→ the external service validates it via JWKS — no shared API keys
→ operations execute as the authenticated user
| Service | Capability | Per-User Auth |
|---|---|---|
| Snowflake | Data warehouse queries | ✅ External OAuth |
| EIA | U.S. energy data analytics | Service account |
| Weather | Real-time weather data | Service account |
| EODHD | Financial market data | Service account |
| Browser Automation | Web scraping, screenshots, PDFs | Service account |
| Notifications | Email, Slack, webhooks | Service account |
| Alpha Vantage | Financial data — 113 tools (equities, forex, crypto, indicators) | Service account |
| Token Validator | JWT/JWKS integration & trust-level debugging | ✅ Per-user JWT |
Any MCP service can register with the Hub in one command:
registry(action: "register", {
name: "my-service",
description: "What your service does",
endpoint: "https://my-service.com/mcp",
category: "data-services"
})
Services that support External OAuth (like Snowflake, Databricks) get per-user authentication automatically.
https://paichart.app/api/auth/jwks/prompt list) in your AI clientmcp mcp-hub mcp-server mcp-orchestration model-context-protocol ai-native delivery-management proof-of-value pov task-management project-management ai-services service-discovery external-oauth jwks per-service-audience rfc8707 per-user-authentication workflow-orchestration error-recovery mcp-tutorials claude-desktop chatgpt snowflake context7
makafeli/n8n-workflow-builder
danishashko/make-mcp
lukisch/n8n-manager-mcp
io.github.us-all/airflow
io.github.infoinlet-marketplace/mcp-workflow