Pipes MCP Server
Interact with third-party APIs using human-approved, provider-scoped access control.
Data last scanned today · Reviewed today
Overview
Pipes MCP Server functions as a template for integrating AI assistants with external services like Linear, Notion, and Snowflake. It prioritizes security through a human-in-the-loop workflow, where AI requests for elevated access require manual approval via a browser-based consent screen. This approach ensures that actions are not taken without user verification. The system utilizes provider-scoped authority, allowing users to authorize specific integrations rather than granting blanket permissions. Authority is managed through time-limited sessions, expiring by default after five minutes. Operations are further controlled by distinct read and write gating, ensuring that AI-initiated API calls remain within strictly defined scopes.
Our verdict
With a security score of 71/100, this server is rated as medium risk. The primary security concern is that it lacks a strictly enforced read-only mode, meaning all installations have the potential for full write access if improperly configured. However, it mitigates these risks through a robust human-in-the-loop approval flow for all elevated API actions. It is suitable for developers who require fine-grained access control over AI tool usage and are comfortable managing the provided approval infrastructure.
- Human-in-the-loop approval flow for all elevated actions
- Time-limited sessions expire after five minutes by default
- Provider-scoped authority prevents all-or-nothing access grants
- Read and write operations are gated separately
- No default read-only mode prevents full write access
- Not yet subject to independent editorial security review
Setup
{
"servers": {
"pipes-mcp": {
"args": [
"-y",
"pipes-mcp"
],
"command": "npx"
}
}
}Paste into .vscode/mcp.json in your workspace (or run "MCP: Open User Configuration" for a global config). Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
Tools
| Tool | Description | Risk |
|---|---|---|
| request_elevated_access | Requests temporary elevated access for selected providers. | medium |
| check_access_request | Checks the status of an access request and retrieves associated instructions. | low |
| call_integration_api | Executes an API call to an integrated provider. | high |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the core technical prerequisites for running this server?
You need Node.js 20+, pnpm, and an active Redis instance. You must also have a WorkOS account configured with both AuthKit and Pipes.
›How long does granted authority last?
By default, authority sessions expire after 5 minutes, but this can be adjusted by modifying the SESSION_AUTHORITY_TTL_MS environment variable.
›Is the approval process strictly for individual API calls?
No, the server supports both 'broad' grants for temporary session authority and 'request' grants for approving a single, specific API call.
›How do I connect my MCP client to the server?
Point your MCP client (such as Claude Desktop or Cursor) to the server's URL, specifically using the path http://localhost:5711/mcp.
›What is the role of Redis in this setup?
Redis is used for storing session records, authority grant states, and approval token consumption tracking.
›Does the server require authentication for all MCP requests?
Yes, every MCP request is authenticated via AuthKit before it is authorized through the active Pipes session and grant state.
Badge
Maintain this server? Add the live badge to your README.