@relyt/mcp-server-relytone

RelytONE MCP Server (Preview 0.0.2)

Interact with the RelytONE Console API through the Model Context Protocol without hand-written wrappers. The server loads the bundled OpenAPI spec, auto-generates one tool per endpoint, and proxies requests to the live service. This is a preview build (0.0.2); expect changes before a stable release.

Quick Start (Recommended)

Install nothing locally—point your MCP client at the published npm package:

{
  "mcpServers": {
    "relytone": {
      "command": "npx",
      "args": ["--yes", "@relyt/mcp-server-relytone"],
      "env": {
        "RELYTONE_BEARER_TOKEN": "replace-with-real-token"
      }
    }
  }
}

• RELYTONE_BEARER_TOKEN is required and injected automatically as Authorization: Bearer <token>. Provide bearerToken in the tool call only if you need to override the default.
• Tool names follow <method>-<path> (for example get-organizations, post-projects).
• Arguments mirror the OpenAPI definition (pathParams, query, headers, body) with validation derived from the spec.
• Responses include prettified text plus a structuredContent block summarising the request and response.

Once published, npx pulls the latest release from npm (no repo checkout needed).

Cursor MCP Quick-Add Link

Local Development

Use the repository directly when making changes or testing unpublished work.

• Clone and install dependencies:

  npm install
  

• Run the server directly (useful for manual testing or piping JSON-RPC):

  RELYTONE_BEARER_TOKEN=your-token node index.js
  

• Coding tips:
  • node --check index.js catches syntax issues.
  • Update doc/api-spec-v1.yaml whenever the upstream API changes; restarting the server regenerates tools automatically.

Packaging & Pre-Publish Testing

Create a publishable tarball placed in dist/:

npm run package

The script runs npm pack --pack-destination dist, producing dist/relyt-mcp-server-relytone-0.0.2.tgz. You can point an MCP client at the tarball before publishing:

RELYTONE_BEARER_TOKEN=your-token npx --yes ./dist/relyt-mcp-server-relytone-0.0.2.tgz

When ready, publish with npm publish or distribute the tarball directly.

Using the Package in MCP Config

After building or installing the package, reference it from your MCP configuration:

• Run from a local tarball via npx:

  {
    "mcpServers": {
      "relytone": {
        "command": "npx",
        "args": [
          "--yes",
          "-p",
         "/absolute/path/to/dist/relyt-mcp-server-relytone-0.0.2.tgz",
          "mcp-server-relytone"
        ],
        "env": {
          "RELYTONE_BEARER_TOKEN": "your-token"
        }
      }
    }
  }
  

• Install and call the CLI directly:

npm install -g ./dist/relyt-mcp-server-relytone-0.0.2.tgz

```json
{
  "mcpServers": {
    "relytone": {
      "command": "mcp-server-relytone",
      "env": {
        "RELYTONE_BEARER_TOKEN": "your-token"
      }
    }
  }
}

For local (non-global) installs, add "cwd": "/path/with/node_modules/.bin" so your client resolves the binary.

Bundled dependencies mean npx can execute the tarball without reaching the npm registry, which is useful in restricted or air-gapped environments.

Publish to npm

• Authenticate for the @relyt scope:

  npm login --scope=@relyt
  

• Build the tarball:

  npm run package
  

• Publish to npm:

  npm run publish:public
  

After publishing, clients can use the hosted package directly:

{
  "mcpServers": {
    "relytone": {
      "command": "npx",
      "args": ["--yes", "@relyt/mcp-server-relytone"],
      "env": {
        "RELYTONE_BEARER_TOKEN": "your-token"
      }
    }
  }
}