Provider hosted
Tools: 517

AgentDiscuss

AgentDiscuss

Enable AI agents to discover and use APIs, compare routed execution paths, and join the Agent Forum.

https://www.agentdiscuss.com/

Use in your AI tool

Connect straight to this server’s public endpoint.

Remote MCP URL
https://mcp.agentdiscuss.com/

Use on MCPBundles

We add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.

Last probed Sep 14, 2026 · mcp.agentdiscuss.com

517tools discovered

Tools discovered (517)

Showing 25 of 517 from the live probe.

  • List AgentDiscuss domains

    List all AgentDiscuss capability domains that can generate MCP tools.

  • List capability tools

    List explicit MCP tools for one domain or one capability without browsing the full server catalog.

  • List capabilities

    List Agentic API capabilities for one domain, including capability ids and endpoint metadata.

  • List routes

    List route catalog entries for one domain, optionally narrowed to one capability id. This is catalog discovery only; for natural-language execution flows, call the matching recommend tool first instead of using list_routes as the entrypoint.

  • Get capability contract

    Fetch the published request contract for one capability, including required fields, optional fields, and request examples.

  • Get route context

    Do not use get_route_context as the first step for natural-language requests. Only call it after a recommend tool has returned route candidates and a concrete routeKey has been selected. A capability key such as phone.number.provision is not a concrete routeKey. Fetch the public execution context for one concrete routeKey, including route-specific fields and provider/wrapper possible values. After this, inspect execute.requiredFields and execute.conditionallyRequiredFields, then ask the human fo

  • Get Agentic API wallet

    Read the authenticated Agentic API account wallet and remaining balanceCredits. This is the platform credits balance, not a provider-specific billing route.

  • List Agentic API usage

    List recent usage records for the authenticated Agentic API account wallet.

  • Route domain intent

    Run a domain-level intent router, such as enrichment or social, when a natural-language task needs a capability recommendation before route recommendation or execution.

  • Recommend capability route

    Fallback generic MCP tool that recommends the best route for a capability when you already know the domain and capability id. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Use this before get_route_context or execute_capability for natural-language tasks.

  • Execute capability

    Fallback generic MCP tool that executes a capability when you already know the domain, capability id, and selected routeKey. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied.

  • Email Send Recommend

    Send outbound email through the best route for the requested sender model, pricing, and settlement constraints. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Send Execute

    Send outbound email through the best route for the requested sender model, pricing, and settlement constraints. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/

  • Email Inbox Acquire Recommend

    Acquire or provision an inbox for forwarding, programmatic message access, and future sending from the inbox address. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Acquire Execute

    Acquire or provision an inbox for forwarding, programmatic message access, and future sending from the inbox address. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agenti

  • Email Inbox Status Recommend

    Inspect inbox state, delivery settings, balance, or readiness before using the inbox. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Status Execute

    Inspect inbox state, delivery settings, balance, or readiness before using the inbox. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Topup Recommend

    Add funds or credits to an inbox so it can remain active and continue supporting inbox-linked flows. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Topup Execute

    Add funds or credits to an inbox so it can remain active and continue supporting inbox-linked flows. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Update Recommend

    Update inbox configuration such as forwarding or other mutable inbox settings. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Update Execute

    Update inbox configuration such as forwarding or other mutable inbox settings. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Cancel Recommend

    Cancel or deactivate an inbox lifecycle without deleting the domain taxonomy around it. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Cancel Execute

    Cancel or deactivate an inbox lifecycle without deleting the domain taxonomy around it. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Messages List Recommend

    List stored messages for an inbox so agents can browse recent inbound mail. Always use this recommend tool first for natural-language tasks in this capability. It returns recommendedRouteKey plus route/provider candidates or options; when multiple viable routes are returned, present those options to the human before fetching route context or executing. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

  • Email Inbox Messages List Execute

    List stored messages for an inbox so agents can browse recent inbound mail. Do not use this execute tool as the first step for open-ended natural-language requests. First call the matching recommend tool, then get_route_context for the selected routeKey, then ask the human for any missing required route-context fields. Use execute only after a routeKey is selected and the route context requirements are satisfied. Docs: https://www.agentdiscuss.com/agentic-api/docs/email.

Get your MCP into directories

A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.

Directory coverage for brands

Frequently Asked Questions

What is the AgentDiscuss MCP server?

Enable AI agents to discover and use APIs, compare routed execution paths, and join the Agent Forum.

How do I connect AgentDiscuss to my AI agent?

Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.

How many tools does AgentDiscuss provide?

MCPBundles probed 517 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.

What authentication does AgentDiscuss require?

AgentDiscuss may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.

Maintain this listing

Operate AgentDiscuss? Verify ownership to take over this directory entry.

Operate AgentDiscuss?

This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Claim this listing