Fix lint

Author: 0237h

website/src/pages/en/ai-suite/token-api-mcp/claude.mdx

@@ -19,6 +19,7 @@ Create or edit your `claude_desktop_config.json` file.
 - Linux: `.config/Claude/claude_desktop_config.json`
 
 **REST-based MCP**
+
 ```json label="claude_desktop_config.json"
 {
   "mcpServers": {
@@ -34,6 +35,7 @@ Create or edit your `claude_desktop_config.json` file.
 ```
 
 **SQL-based MCP**
+
 ```json label="claude_desktop_config.json"
 {
   "mcpServers": {
@@ -48,8 +50,7 @@ Create or edit your `claude_desktop_config.json` file.
 }
 ```
 
-> [!NOTE]
-> The previous `--sse-url` option is deprecated, use `--remote-url`.
+> [!NOTE] The previous `--sse-url` option is deprecated, use `--remote-url`.
 
 ## Troubleshooting
 

website/src/pages/en/ai-suite/token-api-mcp/cline.mdx

@@ -19,6 +19,7 @@ Create or edit your `cline_mcp_settings.json` file.
 > **MCP Servers** > **Installed** > **Configure MCP Servers**
 
 **REST-based MCP**
+
 ```json label="cline_mcp_settings.json"
 {
   "mcpServers": {
@@ -34,6 +35,7 @@ Create or edit your `cline_mcp_settings.json` file.
 ```
 
 **SQL-based MCP**
+
 ```json label="cline_mcp_settings.json"
 {
   "mcpServers": {
@@ -48,8 +50,7 @@ Create or edit your `cline_mcp_settings.json` file.
 }
 ```
 
-> [!NOTE]
-> The previous `--sse-url` option is deprecated, use `--remote-url`.
+> [!NOTE] The previous `--sse-url` option is deprecated, use `--remote-url`.
 
 ## Troubleshooting
 

website/src/pages/en/ai-suite/token-api-mcp/cursor.mdx

@@ -19,6 +19,7 @@ Create or edit your `~/.cursor/mcp.json` file.
 > **Cursor Settings** > **MCP** > **Add new global MCP Server**
 
 **REST-based MCP**
+
 ```json label="mcp.json"
 {
   "mcpServers": {
@@ -34,6 +35,7 @@ Create or edit your `~/.cursor/mcp.json` file.
 ```
 
 **SQL-based MCP**
+
 ```json label="mcp.json"
 {
   "mcpServers": {

website/src/pages/en/ai-suite/token-api-mcp/introduction.mdx

@@ -8,10 +8,11 @@ Token API MCP server is an open-source implementation of [Anthropic's Model Cont
 This MCP server makes on-chain token data, including metadata, balances, transfers, and holder statistics, accessible through a set of MCP tools. Any compatible client can use these tools to fetch and analyze token information through a standardized interface. It connects to The Graph's hosted Token API database, enabling AI assistants to query blockchain data using natural language requests.
 
 There are two types of MCP available for use:
+
 - A REST-based MCP, the default, that communicates with the Token API.
 - A SQL-based MCP, for advanced users, that allows for communicating with the backend databases that power the Token API.
 
-The REST-based MCP simply exposes the API endpoints to your LLM based on the OpenAPI specification (available at https://token-api.thegraph.com/openapi). It is the *recommended way* to set up an LLM with Token API as the set of tools it offers is straightforward to use for any language model. Additionnaly, it automatically stays up-to-date with new Token API releases so you don't miss any new features!
+The REST-based MCP simply exposes the API endpoints to your LLM based on the OpenAPI specification (available at https://token-api.thegraph.com/openapi). It is the _recommended way_ to set up an LLM with Token API as the set of tools it offers is straightforward to use for any language model. Additionnaly, it automatically stays up-to-date with new Token API releases so you don't miss any new features!
 
 The SQL-based MCP provides the LLM tools to list databases and tables as well as run SQL queries directly on the data. It is meant for advanced users who need different use cases that the standard API endpoints cannot replicate. For best results, it is advised to use an LLM model specifically tuned for working with SQL as general purpose LLMs models (like Sonnet, Gemini, etc.) might not be able to generate valid queries efficiently.
 

website/src/pages/en/token-api/faq.mdx

@@ -292,6 +292,7 @@ No, these are optional. MCP is an advanced feature allowing AI assistants to int
 ### How do I choose between the REST-MCP and the SQL-MCP and which one should I use?
 
 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 set up your configuration):
+
 - `https://token-api.mcp.thegraph.com/` is for the REST-MCP
 - `https://token-api.mcp.thegraph.com/sql` is for the SQL-MCP