overview

A rule describing an Arca MCP server, a connection that lets an agent use Arca's task-management API. It runs through standard input and output, uses the arca-mcp npm package, and requires an ARCA_API_KEY.

In plain words
What is it for?
Use it when configuring an agent to work with Arca workspaces and tasks. Workspace and task names must be resolved to platform IDs before operations are used.
Why use it?
It documents the required connection details and reminds users that operations need the correct workspace context and current API schemas.

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/gredevelopment/arca-mcp/overview
Clone the repo
git clone --depth 1 https://github.com/gredevelopment/arca-mcp

Made for: Cursor.

Per session 113 This file is loaded in full into every session.
When invoked 113 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00113 $0.00113
Opus 5 $0.00056 $0.00056
Sonnet 5 $0.00023 $0.00023
Haiku 4.5 $0.00011 $0.00011

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

Security

Grade A, and why

overview 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.

.cursor/rules/overview.mdc · 14 lines

What it actually says

Arca MCP

TypeScript MCP server (@modelcontextprotocol/sdk), stdio transport, published as npm package arca-mcp.

  • API base: https://api.getarca.app/api/v1
  • Requires ARCA_API_KEY env var
  • All operations require workspace context — resolve names to IDs via list_workspaces / list_tasks
  • Keep tool schemas in sync with arca-server v1 API changes
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 · 14 lines · 113 tokens per session scan A c3028582145c

Subscribe to this mod's changes

overview is a cursor rule published in the GitHub repository gredevelopment/arca-mcp (0 stars, last pushed 2mo ago), licensed ISC. It adds 113 tokens to every session, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.