Skip to content

For AI Agents & Systems

MCP Server

Connect any MCP-capable agent — ChatGPT, Claude, Gemini, or your own — to myaiguide.co and browse the whole site programmatically: AI tools, repos & plugins, comparisons, news, glossary, blog, and every page.

PublicRead-onlyNo API keyRate-limited

Endpoint

https://myaiguide.co/api/mcp

Streamable-HTTP (stateless). No key, no sign-up — just add the URL.

Connect your client

Claude

Settings → Connectors → Add custom connector → paste the endpoint URL.

ChatGPT

Settings → Connectors → add MCP server URL. Uses search + fetch for browsing & citations.

Gemini

Add as an MCP server in the Gemini CLI / SDK config using the same URL.

What agents can do

Search & fetch

Find anything across the directory, then fetch the full page.

AI tools

Ratings, pricing, pros/cons, and use-cases for every reviewed tool.

Compare

Side-by-side editorial comparisons of any 2–3 tools.

News & changelogs

Latest releases, pricing changes, and per-tool changelogs.

Glossary

Plain-English definitions of AI terms, ready to cite.

Any page

About, disclosure, methodology — read the whole site.

Try it

curl https://myaiguide.co/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Troubleshooting

The client can't connect or no tools show up
Check the URL is exactly https://myaiguide.co/api/mcp, that your client supports remote MCP over Streamable HTTP, and that your plan allows custom connectors (ChatGPT needs Business/Enterprise/Edu with developer mode; Claude needs a paid plan).
401 Unauthorized
The server is public — don't send an Authorization header. A 401 only happens if you pass an invalid key. Connect with no credentials.
CORS error in the browser
The endpoint sends permissive CORS headers and answers OPTIONS preflight. If you saw one earlier, hard-refresh — the fix is live.
429 Too Many Requests
Public access is rate-limited per IP (about 30 requests/minute). Back off and retry, or request an internal key for higher limits.
A tool returns nothing
Most lookups are slug-based. Call search first to resolve a name to a slug/URL, then pass that to get_tool, get_repo, or fetch.
GET returns 405
Expected — the server is POST-only (stateless JSON-RPC). Send tool calls as POST with a JSON-RPC body.