OneSchema MCP Server

co.oneschemaPublished by oneschema.coOfficial publisherv1.0.1Updated Oct 25, 2026

MCP server that lets AI assistants use all OneSchema features exposed via the public API.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI assistant use OneSchema features exposed through the OneSchema public API.

What you can do
Connect an assistant to OneSchema through its public API, so OneSchema capabilities can be used from within a conversation. The manifest lists no individual tools, so the exact actions depend on what the OneSchema public API exposes. Access is authenticated with a OneSchema API key sent in a request header.
When to use it
Useful when you already work with OneSchema and want an assistant to reach its features through the public API without leaving the chat. It is not worth adding if you do not have a OneSchema account or API key.
Requirements
A remote streamable HTTP endpoint at api.oneschema.co; no local package or runtime is needed. A OneSchema account and API key are required, supplied in the X-Api-Key header. Network access to the endpoint is needed.
Before you install
The server requires your OneSchema API key in the X-Api-Key header, so treat it as a secret and avoid exposing it in shared logs or transcripts. Because it exposes all OneSchema features available through the public API, actions may read or change data in your OneSchema account; confirm what the connected tools can do before relying on them.

Installation

In SourceWeft

  1. Open OneSchema MCP Server in the dashboard and add it to a workspace.
  2. Connect X-Api-Key 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/co.oneschema%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": {
    "oneschema": {
      "type": "http",
      "url": "https://api.oneschema.co/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

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