Skip to main content
Glama

Cookiecat

Cookiecat is a Cursor/Agent MCP plugin that wraps RelayRouter’s OpenAI-compatible API: list models and run non-streaming chat completions.

Ownership: Meyra
Version: 0.1.0
License: MIT
Tools: list_models, chat_completion (non-streaming)

Secrets

Never commit API keys. Set them only via:

  1. Cursor → Plugins → Configure (plugin variables RELAYROUTER_API_KEY, optional RELAYROUTER_BASE_URL), or

  2. A local gitignored .env (copy from .env.example) / shell export for smoke tests.

Default base URL: https://api.relayrouter.ai/v1 (also compatible with https://relayrouter.io/v1).

Related MCP server: rapidrouter-mcp

Install (developers)

cd /path/to/cookiecat   # or this repo
npm install
npm run bundle          # writes dist/cookiecat.mjs (SDK + zod inlined)

Marketplace / clone installs should ship dist/cookiecat.mjs so node can start without node_modules.

Cursor plugin folder

  • Add this folder as a plugin, or clone into the plugin search path.

  • mcp.json runs: node ${CURSOR_PLUGIN_ROOT}/dist/cookiecat.mjs

  • Configure RELAYROUTER_API_KEY (required) and optional RELAYROUTER_BASE_URL in Plugins → Configure.

MCP-only (no plugin shell)

{
  "mcpServers": {
    "cookiecat": {
      "command": "node",
      "args": ["/absolute/path/to/cookiecat/dist/cookiecat.mjs"],
      "env": {
        "RELAYROUTER_API_KEY": "YOUR_KEY_FROM_CONFIGURE_OR_ENV",
        "RELAYROUTER_BASE_URL": "https://api.relayrouter.ai/v1"
      }
    }
  }
}

For source hot-reload during development: "command": "npx", "args": ["tsx", "/absolute/path/to/src/index.ts"] (needs npm install).

Verify

npm run bundle
npm run typecheck
# missing key → clear error:
RELAYROUTER_API_KEY= npm run smoke
# with key → list_models + short chat:
npm run smoke

Scripts

Command

Purpose

npm run bundle

esbuild → single dist/cookiecat.mjs

npm run build

tsc then bundle

npm start

node dist/cookiecat.mjs (stdio MCP)

npm run dev

tsx src/index.ts

npm run typecheck

typecheck only

npm run smoke

API smoke without an MCP client

Security

  • .gitignore ignores node_modules, .env, *.key; keeps dist/cookiecat.mjs for clone-runnable installs

  • Logs/replies mask keys (at most first 4 + last 4 chars)

  • Do not put real secrets in the repo or Marketplace forms

Available Tools

2 tools
chat_completionB

Non-streaming chat completion via RelayRouter (POST /v1/chat/completions, stream=false). Returns assistant content and usage.

Inputs: model (required), messages (required), stop, tools, +3 more.

list_modelsA

List models available on RelayRouter (GET /v1/models). Returns model ids and any upstream fields such as object/owned_by.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available models and the other performs a chat completion. There is no meaningful overlap in resource or action.

    Naming Consistency4/5

    Both names use snake_case and are readable, but the pattern is not fully uniform: list_models is verb_noun while chat_completion is noun-oriented without a clear verb. Minor deviation only.

    Tool Count3/5

    Two tools is thin for a RelayRouter-style server, even if the immediate scope is minimal. It covers a basic workflow but leaves little room for common adjacent operations.

    Completeness3/5

    The surface includes model listing and non-streaming chat completion, but omits obvious adjacent capabilities such as streaming responses or richer model retrieval. Core chat use is covered, with notable gaps for a fuller API wrapper.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers