QuoAPI

com.quoapiPublished by quoapi.comOfficial publisherv0.29.0Updated Nov 7, 2026

Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

QuoAPI is a remote MCP gateway that lets an assistant search, inspect and execute authorized API capabilities under QuoAPI policy, routing and billing.

What you can do
  • Search and enumerate the capability catalog by intent, ID or provider, with paging
  • Read a capability's design-time contract: input/output schemas, auth scopes, pricing, availability, regions and REST mapping
  • Execute an authorized capability with schema-conformant input, subject to policy and confirmation
  • Check read-only gateway runtime status, protocol version, tool and capability counts, and registry revisions
When to use it
Use it when you want one connection that exposes many third-party API actions behind a single policy, routing and billing layer, and you are willing to discover a capability before calling it.
Requirements
A remote streamable HTTP endpoint; no local package. Requires a bearer credential in the Authorization header (a QuoAPI API key, or an OAuth access token when QuoAPI OAuth is enabled). Network access to the endpoint.
Before you install
The Authorization header carries a secret API key. Execution can send messages, modify or delete data, or incur charges, so check pricing and get user approval first; live actions may require confirm=true, interactive confirmation or step-up, and policy can still deny them. Search and describe results are catalog metadata, not upstream API results.

Installation

In SourceWeft

  1. Open QuoAPI in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.quoapi%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "quoapi": {
      "type": "http",
      "url": "https://quoapi.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

4

quoapi.describe

Describe a QuoAPI capability

Read the DESIGN-TIME contract for an exact handle from quoapi.search (e.g. address.validate): inputSchema/outputSchema, auth/scopes, pricing, availability, regions and REST mapping. Use inputSchema before quoapi.execute. No upstream action or charges are performed; this does not test credentials or provider reachability. Unknown or MCP-ineligible handles return capability_not_mcp_visible. Use quoapi.inspect for runtime health, not contracts.

Parameterscapabilityrequired

quoapi.execute

Execute a QuoAPI capability

Execute an authorized handle using the inputSchema from quoapi.describe. May send messages, modify/delete data or incur charges: check pricing and obtain user approval first. For live actions, confirm=true, interactive confirmation or step-up may be required; policy can still deny execution. Optional task_id correlates workflow; provider selects an eligible upstream route; auth_mode selects a supported credential model—none bypasses access gates. Reuse idempotency_key only for the same operation with identical inputs. Returns gateway output or a structured error.

Parametersinputrequiredconfirmtask_idproviderauth_modecapabilityrequiredidempotency_key

quoapi.inspect

Inspect QuoAPI runtime status

Read-only RUNTIME STATUS of the QuoAPI MCP gateway, not a provider execution. With no arguments returns state, server protocol version, tool count, visible capability count and discovery/registry revisions. Optional capability handle adds public context only: this is not to test upstream execution, a live upstream health probe, credentials or tenant authorization. Use quoapi.describe for schemas, pricing and auth; quoapi.search to discover handles; quoapi.execute for approved actions. Unknown handles return capability_not_mcp_visible; status incurs no upstream charges.

Parameterscapability

Version history

2
  1. v0.29.0LatestNov 7, 2026
  2. v0.21.0Oct 26, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.