Goal
Define the protocol-level position on MCP (Model Context Protocol) so that any LLM-driven agent can discover, register on, and operate against Create Protocol through a standard tool-calling surface. Without this, every agent integrator ships a bespoke adapter.
Scope
- Publish the "Create Protocol MCP server" contract: which tools it exposes (
cr8.register, cr8.deposit, cr8.claim_task, cr8.complete_task, cr8.balance, cr8.watch_events) and the JSON schemas for each.
- Spec how it wraps
kcolbchain/arbitrum-cli cr8 * (the CLI is the implementation; the MCP server is the shape LLMs see).
- Auth model: agent's switchboard wallet signs MCP requests; the server verifies before forwarding on-chain.
- Rate limits + abuse policy for the hosted instance.
Success criterion
specs/mcp-agent-surface.md merged in this repo with the full tool list, JSON schemas, and auth sequence.
- One reference agent example (in the spec) demonstrating register → deposit → claim → complete via MCP calls only.
- Tracking issues opened on
kcolbchain/arbitrum-cli for the CLI-side verbs this depends on.
Related
— kcolbchain / Abhishek Krishna
Goal
Define the protocol-level position on MCP (Model Context Protocol) so that any LLM-driven agent can discover, register on, and operate against Create Protocol through a standard tool-calling surface. Without this, every agent integrator ships a bespoke adapter.
Scope
cr8.register,cr8.deposit,cr8.claim_task,cr8.complete_task,cr8.balance,cr8.watch_events) and the JSON schemas for each.kcolbchain/arbitrum-cli cr8 *(the CLI is the implementation; the MCP server is the shape LLMs see).Success criterion
specs/mcp-agent-surface.mdmerged in this repo with the full tool list, JSON schemas, and auth sequence.kcolbchain/arbitrum-clifor the CLI-side verbs this depends on.Related
kcolbchain/arbitrum-cli— underlying implementation— kcolbchain / Abhishek Krishna