MCPist
Provides tools for managing Airtable bases, tables, and records.
Enables AI assistants to manage projects, tasks, and teams within Asana.
Connects AI assistants to Confluence for managing spaces, pages, and organizational content.
Allows AI tools to interact with Dropbox for file and folder management.
Provides capabilities to interact with GitHub repositories, issues, and pull requests.
Connects AI assistants to Google Workspace tools including Sheets, Docs, Drive, Calendar, and Tasks.
Enables querying and management of Grafana dashboards and observability data.
Allows management of Jira issues, projects, and development workflows.
Provides tools to manage Notion databases, pages, and workspace organization.
Enables AI assistants to perform queries and manage data within PostgreSQL databases.
Allows for managing tasks, lists, and reminders within the TickTick platform.
Enables interaction with Todoist for task, project, and reminder management.
Provides capabilities to manage Trello boards, lists, and cards.
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., "@MCPistcreate a Notion page summarizing my recent Jira issues"
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.
MCPist
MCP (Model Context Protocol) gateway service — Connect AI assistants to external tools through a single endpoint.
Usage
Add to your MCP client configuration (Claude Code, Cursor, etc.):
{
"mcpServers": {
"mcpist": {
"url": "https://mcp.mcpist.app/v1/mcp",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
}
}Get your API key at mcpist.app.
Related MCP server: RL-MCP
Supported Modules
Notion, GitHub, Jira, Confluence, Google Workspace (Sheets, Docs, Drive, Calendar, Tasks), Todoist, TickTick, Microsoft Todo, Asana, Trello, Airtable, Dropbox, PostgreSQL, Grafana, and more.
Architecture
Console (Next.js / Vercel)
↓
Worker (Cloudflare Workers) — Auth + Routing
↓
Server (Go / Render) — MCP Handler + REST API
↓
PostgreSQLAuthentication
User auth: Clerk (JWT) via Console
API keys: Ed25519 JWT issued by Server
Gateway auth: Worker signs short-lived JWT for Server-to-Server trust
Tech Stack
Layer | Technology |
Frontend | Next.js 16, React 19, Tailwind CSS, Radix UI |
API Gateway | Cloudflare Workers, Hono, TypeScript |
Backend | Go 1.24, GORM |
Database | PostgreSQL |
Auth | Clerk, Ed25519 JWT |
Billing | Stripe |
Observability | Grafana Loki |
Monorepo | pnpm workspaces, Turborepo |
Development
Prerequisites
Node.js 20+
pnpm 9
Go 1.24+
Docker Desktop
Setup
pnpm install
cp .env.example .env.local # Edit with your values
pnpm env:syncRun
pnpm devStarts PostgreSQL (Docker), Console, Server, and Worker concurrently.
Service | URL | Description |
PostgreSQL | localhost:57432 | Database (Docker) |
Console | Web UI | |
Server | MCP Server | |
Worker | API Gateway |
pnpm db:down # Stop PostgreSQL containerScripts
Command | Description |
| Start DB + all apps |
| Start PostgreSQL only |
| Stop PostgreSQL |
| Console only |
| Go Server only (Air hot reload) |
| Worker only (Wrangler) |
| Build all apps (Turbo) |
| Lint all apps |
| Run tests |
| Distribute .env.local to each app |
| Generate ER diagram from schema |
Project Structure
mcpist/
├── apps/
│ ├── console/ # Web UI
│ ├── server/ # MCP Server + REST API
│ └── worker/ # API Gateway
├── database/
│ └── migrations/ # PostgreSQL schema
├── docs/ # Specifications & design docs
├── scripts/ # Dev utilities
└── .github/workflows/ # CIDeployment
App | Platform | Domain |
Console | Vercel | mcpist.app |
Worker | Cloudflare Workers | mcp.mcpist.app |
Server | Render | mcpist.onrender.com |
Database | Neon | — |
API Specification
OpenAPI 3.1 spec: GET /openapi.json
Source: apps/worker/src/openapi.yaml
This server cannot be deployed
Maintenance
Related MCP Connectors
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceA unified Model Context Protocol Gateway that bridges LLM interfaces with various tools and services, providing OpenAI API compatibility and supporting both synchronous and asynchronous tool execution.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.2-
- AlicenseNot gradedqualityCmaintenanceA unified Model Context Protocol server that provides a consistent interface for AI assistants to interact with productivity tools like Linear, GitHub, Slack, and Notion. It enables users to search, retrieve, and manage tasks and data across multiple workplace services from a single endpoint.15 npmMIT
- FlicenseNot gradedqualityDmaintenanceA unified gateway for AI agent tools that provides a single MCP stdio endpoint for executing tool calls with unified auth, rate limiting, and observability. Enables agents to interact with multiple external APIs through a standardized interface.1-