Update Token API MCP documentation

[0237h]

introduction.mdx

• Adds the two types of MCP
• Emphasizes REST easier to use for LLMs than SQL
• Misc editing

claude.mdx

• Adds REST MCP config
• Updates config commands
• Adds depreciation notice for --sse-url option
• Improves troubleshooting section

cline.mdx
Same as Claude

cursor.mdx
Same as Claude

faq.mdx

• 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 ?

[0237h]

Realized this one might be poorly formulated:

How do I choose between the REST-MCP and the SQL-MCP and which one should I use ?

I meant:

How do I toggle between the REST-MCP and the SQL-MCP and which one should I use ?

But maybe that's still not clear enough and can be separated into two. The idea is to ask about the configuration aspect of choosing REST/SQL (answer is, use the adequate URL) and to ask about the use cases for one or the other.

So maybe two questions:

Can I use both MCPs at the same time ?
No, you choose which MCP to use based on the remote URL, ...

and

Which MCP should I use ?
...

[matthewdarwin]

We should definately suggest to users to use the REST MCP as the SQL one is easy to get things wrong and generate inefffient queries. By default use that one unless there is some special need to use SQL.

In this PR we won't address pricing for SQL MCP, other than you need to be on PRO or ENTERPRISE plan. Pricing page can be updated in a future PR.

[benface]

Found some typos, but otherwise LGTM.

[benface]

🙌