Perdoo MCP Server
An MCP server that integrates with the Perdoo OKR platform, providing tools to manage objectives, key results, initiatives, KPIs, and strategic pillars.
README
Perdoo MCP Server
An MCP (Model Context Protocol) server that integrates with the Perdoo OKR platform via its GraphQL API. Provides 19 tools for managing objectives, key results, initiatives, KPIs, and strategic pillars.
Features
- Full CRUD for objectives, key results, initiatives, KPIs, and strategic pillars
- Helper tools for looking up timeframes, users, and groups
- Cursor-based pagination on all list operations
- Resilience stack: rate limiting, circuit breaker, retry with exponential backoff, request queuing
- Session-based HTTP transport (Streamable HTTP)
- Instructions resource at
perdoo://instructionsfor LLM guidance
Tools
| Category | Tools |
|---|---|
| Objectives | list_objectives, get_objective, create_objective, update_objective |
| Key Results | list_key_results, get_key_result, create_key_result, update_key_result |
| Initiatives | list_initiatives, get_initiative, create_initiative, update_initiative |
| KPIs | list_kpis, get_kpi, create_kpi, update_kpi |
| Strategic Pillars | list_strategic_pillars, get_strategic_pillar |
| Helpers | list_timeframes, list_users, list_groups |
Setup
Prerequisites
- Node.js >= 18
- A Perdoo API token (generate one in Perdoo settings)
Install and run
git clone https://github.com/nevilhulspas/perdoo-mcp.git
cd perdoo-mcp
npm install
cp .env.example .env
# Edit .env and add your PERDOO_API_TOKEN
npm run build
npm start
The server starts on port 3001 by default.
Development
npm run dev # Watch mode with tsx
Docker
npm run docker:build
npm run docker:run
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
PERDOO_API_TOKEN |
Yes | - | Bearer token for the Perdoo GraphQL API |
PORT |
No | 3001 |
HTTP server port |
NODE_ENV |
No | development |
Environment (development or production) |
MCP Client Configuration
Local
{
"mcpServers": {
"perdoo": {
"url": "http://localhost:3001/mcp"
}
}
}
Remote
When deployed to a remote server with a domain:
{
"mcpServers": {
"perdoo": {
"url": "https://perdoo-mcp.yourdomain.com/mcp"
}
}
}
Remote Deployment (Dokploy)
This server is designed to run remotely via its HTTP transport. The included Dockerfile makes it straightforward to deploy on any container platform. Below are instructions for Dokploy on a VPS (e.g. Hetzner).
1. Create the application
In your Dokploy dashboard:
- Create a new Application
- Set source to Git and point it to this repo (
https://github.com/nevilhulspas/perdoo-mcp.git) - Set build type to Dockerfile (it will auto-detect the
Dockerfilein the repo root)
2. Configure environment variables
In the application's Environment tab, add:
PERDOO_API_TOKEN=your-bearer-token-here
PORT=3001
NODE_ENV=production
3. Configure the domain
In the Domains tab:
- Add your domain (e.g.
perdoo-mcp.yourdomain.com) - Enable HTTPS (Dokploy handles Let's Encrypt automatically via Traefik)
- Set the container port to
3001
4. Health check
Configure the health check in Dokploy to use:
- Path:
/health - Port:
3001 - Expected status:
200
5. Deploy
Click Deploy. Dokploy will build the Docker image and start the container.
Security considerations
The MCP endpoint has no built-in authentication. Anyone who can reach your server can use the Perdoo tools with your API token.
For production deployments, secure the endpoint using one of these approaches:
- Traefik BasicAuth middleware - Add basic auth via Dokploy's Traefik config labels
- API key middleware - Add a custom Express middleware that checks an
Authorizationheader (see Auth section below) - IP allowlisting - Restrict access to known IPs via firewall rules or Traefik's
ipAllowListmiddleware - VPN/Tailscale - Run the server on a private network only accessible via VPN
Session persistence
Sessions are stored in-memory. A container restart (deploy, crash, scaling) drops all active MCP sessions. Clients will need to re-initialize. This is expected behavior for MCP's Streamable HTTP transport.
Resource sizing
The server is lightweight (single-concurrency request queue, no database). A minimal VPS (1 vCPU, 512 MB RAM) is sufficient.
Endpoints
| Method | Path | Description |
|---|---|---|
POST |
/mcp |
MCP request handler (creates sessions on initialize) |
GET |
/mcp |
SSE endpoint for server notifications |
DELETE |
/mcp |
Session termination |
GET |
/health |
Health check (status, version, active sessions) |
Architecture
src/
├── server.ts # Express HTTP server with session management
├── lib/
│ ├── env.ts # Environment validation (Zod)
│ ├── errors.ts # Typed error classes
│ └── logger.ts # Structured logging
├── mcp/
│ ├── index.ts # MCP server factory
│ └── tools/ # Tool definitions (one file per entity)
└── services/perdoo/
├── client.ts # GraphQL client with resilience stack
├── types.ts # TypeScript types and enums
├── operations/ # GraphQL queries and mutations
├── circuit-breaker.ts # Fails-open after 5 failures
├── rate-limiter.ts # Token bucket (30 capacity, 3/sec)
├── request-queue.ts # Single concurrent request
└── retry.ts # Exponential backoff (queries only)
Resilience
The client applies a resilience stack in order:
- Request Queue - Ensures only one request at a time
- Circuit Breaker - Opens after 5 consecutive failures, resets after 30s
- Retry - Exponential backoff for queries only (mutations are never retried)
- Rate Limiter - Token bucket with 30 capacity, refilling at 3 tokens/sec
Adding Authentication
The server does not include authentication out of the box. For production use, add a shared-secret middleware:
- Add a
MCP_API_KEYenvironment variable - Add middleware to
src/server.tsthat checks theAuthorization: Bearer <key>header on/mcproutes - Configure your MCP client to send the header:
{
"mcpServers": {
"perdoo": {
"url": "https://perdoo-mcp.yourdomain.com/mcp",
"headers": {
"Authorization": "Bearer your-mcp-api-key"
}
}
}
}
Alternatively, use Traefik's built-in BasicAuth middleware at the reverse proxy level (no code changes required).
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.