Find the right AI tools for any job, task or industry.

TOOLGRAIL / GET STARTED

Documentation

Find AI tools for your work, on the website or inside your assistant.

Use the website

Start with a job, task or industry.

Browse, save and compare

Connect your assistant

Bring the public directory into your chat.

Set up remote MCP

Understand a listing

See sources, review dates and unknowns.

Read the evidence

01 / THE WEBSITE

Start with what you want to do.

  1. Describe your work

    Search for a role, such as teacher, or a task, such as meeting transcription. Choose an industry when you want more context.

  2. Explore the options

    Open a tool to read its capabilities, pricing, limitations and sources. The tools directory also lets you filter by task, industry, pricing model and MCP availability.

  3. Save or compare

    Use Wishlist to revisit a tool, or Compare to place up to four tools side by side. Saved selections stay in this browser and do not sync across devices.

  4. Check before adopting

    Follow the official product and pricing links. ToolGrail helps you discover options; any vendor account, subscription or installation is separate.

02 / YOUR AI ASSISTANT

Connect to ToolGrail with MCP.

MCP lets a compatible AI assistant query the directory on your behalf. You need an assistant that supports remote MCP servers; menu names and access depend on your app and plan.

  1. Add a remote connection

    Open your assistant’s connections or integrations settings, add a remote MCP server, and name it ToolGrail.

  2. Paste the address

    Remote MCP · Streamable HTTP · No sign-in

    Choose no authentication. You do not need a ToolGrail account, API key, OAuth client, or local installation. Keep the trailing slash in the URL.

  3. Connect and try a question

    Your assistant discovers five read-only tools. Ask it to use ToolGrail to find or compare options.

TRY THESE
“Use ToolGrail to find AI tools for a teacher preparing lessons.”
“Compare Claude and ChatGPT, including their limitations and sources.”
“Find meeting transcription tools with an official MCP server.”

Watch the animated connection guide →

What your assistant can access

ToolGrail MCP tools and accepted inputs
ToolPurposeInput and limits
search_toolsSearch ToolGrailA phrase, role, task, industry or tool name; up to 25 results.
get_toolOpen a full profileOne tool slug, such as claude. Includes capabilities and data considerations.
recommend_toolsFind tools for workA role or up to 10 task slugs, with optional industry context.
compare_toolsCompare optionsTwo to four different tool slugs, with shared tasks and industries.
list_taxonomyExplore the directoryRoles, tasks and industries; up to 200 entries per kind and page.

Search and recommendations can filter for tools with an official MCP server, including connection types such as OAuth, API key, no sign-in, or local installation. The response explains the vendor’s connection; it does not install or connect that vendor for you.

Results include ToolGrail page links, official sites, pricing information, evidence levels, sources and review dates. Full profiles also include features, integrations, platforms and data considerations. MCP access does not include visitor wishlists, company submissions, admin records, private files, or the website’s AI skills learning guides.

The server exposes tools, with no separate MCP Resources or Prompts. It does not run background jobs, make purchases, or execute the products it lists.

03 / MAKE AN INFORMED CHOICE

Read the evidence, not just the name.

Each profile states whether it was source reviewed, vendor submitted, site checked, or unconfirmed. An unknown price is not a free price; missing integrations are not proof that a tool has none.

The directory is a published snapshot. Review dates describe when a source was checked, and prices or features can change afterward. Recommendations reflect task and industry fit and the available documentation; they are not independent product ratings or professional advice.

Read the full methodology →

For IT administrators and reviewers

A direct browser visit to the MCP URL can return 405 because MCP clients use POST requests. Cross-site browser requests may be blocked by origin checks; server-side MCP connections are the supported path.