You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Adds `How do I choose between the REST-MCP and the SQL-MCP and which one should I use ?`
- Adds `Will using the REST-MCP counts towards my Token API usage ?`
Copy file name to clipboardExpand all lines: website/src/pages/en/token-api/faq.mdx
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -283,12 +283,26 @@ You can find the code for the MCP client in [The Graph's repo](https://github.co
283
283
284
284
### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this?
285
285
286
-
For "ENOENT" errors, ensure Node.js 18+ is installed and the path to `npx`/`bunx` is correct (consider using full paths in config). "Server disconnected" usually indicates authentication or connectivity issues – verify your `ACCESS_TOKEN` is set correctly and your network allows access to `https://token-api.mcp.thegraph.com/sse`.
286
+
For "ENOENT" errors, ensure Node.js 18+ is installed and the path to `npx`/`bunx` is correct (consider using full paths in config). "Server disconnected" usually indicates authentication or connectivity issues – verify your `ACCESS_TOKEN` is set correctly and your network allows access to `https://token-api.mcp.thegraph.com/`.
287
287
288
288
### Do I need to use MCP or tools like Claude, Cline, or Cursor?
289
289
290
290
No, these are optional. MCP is an advanced feature allowing AI assistants to interface with the API via streaming. For standard usage, simply call the REST endpoints with any HTTP client using your JWT. Claude Desktop, Cline bot, and Cursor IDE integrations are provided for convenience but aren't required.
291
291
292
+
### How do I choose between the REST-MCP and the SQL-MCP and which one should I use ?
293
+
294
+
To use one or the other, you need to supply the adequate URL in your configuration file (see the [docs](https://thegraph.com/docs/en/ai-suite/token-api-mcp/introduction/) for how to setup your configuration):
295
+
-`https://token-api.mcp.thegraph.com/` is for the REST-MCP
296
+
-`https://token-api.mcp.thegraph.com/sql` is for the SQL-MCP
297
+
298
+
Which one you'll want to use depends on your use cases. Most of the time you should use the REST-MCP as it's the simplest way for the LLM to interact with blockchain data from the Token API. If you want answers to basic questions such as `What is the balance of ...`, `How many holders of ...`, etc. the REST-MCP gives your LLM all the tools it needs.
299
+
300
+
The SQL-MCP should be used in an analyst use case where complex aggregations are needed that the Token API doesn't provide on its endpoints. It will require the LLM to discover and craft working SQL queries on the backend databases of the Token API.
301
+
302
+
### Will using the REST-MCP counts towards my Token API usage ?
303
+
304
+
Yes, you need to provide your Token API token to the MCP for authenticating with the Token API. The MCP makes API requests on your behalf when your LLM interacts with it.
0 commit comments