Quickstart
Install, set the credentials, make the first call.
Pick your client. The server runs locally over stdio, or through the hosted runtime.
Tools
What your agent can call.
18 tools, as the package's tools/list returns them.
Names and descriptions come from the package's tools/list (@codespar/mcp-celcoin@0.2.4). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.
Compatibility
MCP is a protocol. Any client that speaks it can mount this server.
Through the CodeSpar runtime, codespar_discover finds this server's tools, and a tools/call runs with the credential connected in your project, a test key included.
Questions
Before you install.
How do I install the Celcoin MCP server?
Run npx -y @codespar/mcp-celcoin@0.2.4 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required. Prefer hosted? Add the CodeSpar endpoint with a test key and connect Celcoin in your project; codespar_discover finds its tools.
What can my agent do with Celcoin?
Celcoin exposes 18 tools for payments. Your agent calls them directly; the full list is above.
How does Celcoin authenticate, and how are credentials stored?
Celcoin uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables. On the CodeSpar runtime the credential you connect is stored encrypted for your organization, the runtime renews the OAuth2 access token, and it adds the token to each provider call, so the agent never handles it.
How does Celcoin handle upstream API changes?
Every server is versioned independently on npm. The command on this page pins 0.2.4, the version whose tools are listed here; your agent keeps running it until you change the version.
Is Celcoin open source? How do I report a bug?
Yes. Celcoin is MIT-licensed and published on npm as @codespar/mcp-celcoin, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.