mcp

A Model Context Protocol (MCP) server that gives AI agents tools for working with the WorkOS API. MCP is a standard connection method between AI applications and external tools or data.

In plain words
What is it for?
Use it to expose WorkOS API operations, such as listing Cloudflare zones, as tools that an MCP-compatible AI client can call.
Why use it?
It provides a consistent way for an AI agent to call WorkOS-related operations instead of requiring a separate custom connection for each tool.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/mcpflow/workos-mcp/mcp
Clone the repo
git clone --depth 1 https://github.com/mcpflow/workos-mcp

Made for: Cursor.

Per session 1,348 This file is loaded in full into every session.
When invoked 1,348 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01348 $0.01348
Opus 5 $0.00674 $0.00674
Sonnet 5 $0.00270 $0.00270
Haiku 4.5 $0.00135 $0.00135

Measured yesterday against content hash 80d6d1bbf71d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

88% identical to mcp — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/mcp.mdc · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Server

Project Context

This is a Model Control Protocol (MCP) server that exposes a set of tools to interact with the WorkOS API.

It uses the workers-mcp package to implement MCP protocol in Cloudflare Workers.

What is MCP?

MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools.

MCP Clients are protocol clients that maintain 1:1 connections with servers.

MCP Servers, such as this one, are lightweight programs that each expose specific capabilities through the standardized Model Context Protocol.

Format for Defining Tools

Each method in the MyWorker class automatically becomes an MCP tool that can be used by AI agents. The method signature and JSDoc comments define how the tool appears to the agent.

/**
 * List all Cloudflare zones for the account.
 * @return {Promise<any>} List of zones.
 */
async listZones() {
    const response = await listZones(this.env);
    return response;
}

For tools with parameters:

/**
 * Create a new DNS record.
 * @param zoneId {string} The ID of the zone to create the record in.
 * @param name {string} The name of the DNS record.
 * @param content {string} The content of the DNS record.
 * @param type {string} The type of DNS record (CNAME, A, TXT, or MX).
 * @return {Promise<any>} The created DNS record.
 */
async createDNSRecord(zoneId: string, name: string, content: string, type: string) {
    return await createDNSRecord(this.env, zoneId, name, content, type);
}

The JSDoc structure is critical:

  • The first line becomes the tool's description
  • Each @param defines a parameter with its type and description
  • The @return specifies what the tool returns

Handling Complex Types (Arrays and Objects)

Read the full file on GitHub · 173 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 173 lines · 1,348 tokens per session scan A 80d6d1bbf71d

Subscribe to this mod's changes

mcp is a cursor rule published in the GitHub repository mcpflow/workos-mcp (0 stars, last pushed 1y ago), licensed MIT. It adds 1,348 tokens to every session, about $0.0067 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to mcp, differing in 30 lines, and is treated as a copy.