The Graph Token MCP Skill

Use this skill to run The Graph Token API MCP operations through uxc.

Reuse the uxc skill for generic protocol discovery, envelope parsing, and error handling rules.

Prerequisites

• - uxc is installed and available in PATH.
• Network access to https://token-api.mcp.thegraph.com/.
• A The Graph Token API API TOKEN (JWT) from https://thegraph.market/dashboard is available for authenticated calls.

Important auth distinction:

• - Do not reuse the thegraph-mcp-skill API key directly.
• INLINECODE8 uses a separate credential sourced from The Graph Market Token API dashboard.
• The value used with Authorization: Bearer ... must be the generated API TOKEN (JWT), not the raw dashboard API key.

Core Workflow

1. 1. Verify endpoint and protocol with help-first probing:

1. 2. Configure a dedicated Token API JWT credential and binding:

1. 3. Use fixed link command by default:

1. 4. Inspect operation schema before execution:

1. 5. Prefer read operations first, then narrower wallet/token/pool queries.

Capability Map

• - Service discovery:

• - Token data:

• - Wallet and transfer data:

• - Market and DEX data:

• - Non-EVM coverage:

Always inspect host help and operation help in the current endpoint version before relying on an operation name or argument shape.

Recommended Usage Pattern

1. 1. Start with network discovery:

1. 2. Confirm the operation and required arguments with -h.
2. Query the narrowest surface first:

1. 4. Expand to broader scans only when needed.

Guardrails

• - Keep automation on JSON output envelope; do not rely on --text.
• Parse stable fields first: ok, kind, protocol, data, error.
• Use thegraph-token-mcp-cli as default command path.
• INLINECODE38 is equivalent to uxc https://token-api.mcp.thegraph.com/ <operation> ... when the same auth binding is configured.
• Use direct uxc "<endpoint>" ... only as temporary fallback when link setup is unavailable.
• Prefer key=value for simple arguments and positional JSON for nested objects.
• If auth fails:

Tested Real Scenario

The endpoint was verified through uxc host discovery and returned a live MCP tool list including:

• - INLINECODE48
• INLINECODE49
• INLINECODE50
• INLINECODE51
• INLINECODE52
• INLINECODE53

This confirms the skill target is a real MCP surface rather than a direct OpenAPI host.

The Token API requires its own bearer token workflow:

• - manage the token in INLINECODE54
• generate API TOKEN (JWT) from the dashboard-managed Token API key
• store that JWT separately from the subgraph MCP credential

Do not document or implement this skill as if it reused the same raw API key as thegraph-mcp-skill.

References

• - Invocation patterns: