Synap

com.linkrraPublished by linkrra.comOfficial publisherv1.2.0Updated Oct 24, 2026

Open AI models through one OpenAI-compatible API: chat, live model list, prices and cost estimates.

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

Synap by Linkrra exposes open AI models through one OpenAI-compatible API, letting an assistant list models, check prices, estimate cost and run chat…

What you can do
  • List the models Synap serves with prices, context windows and strengths
  • Read a single model's full catalogue record: pricing, limits, parameters, quantisation, retention
  • Estimate the token cost of a chat completion before running it
  • Run a chat completion on a Synap model and get the reply back
When to use it
Useful when you want an assistant to generate text or code through Linkrra's hosted open models, or to compare model prices and budget a job before spending anything.
Requirements
Remote Streamable HTTP endpoint at pool.linkrra.com/mcp, or the local stdio bridge via npx synap-mcp (Node 18 or later). A Synap API key is needed only for chat completions, sent as an Authorization Bearer header or the SYNAP_API_KEY variable; the three read-only tools work without one. A funded Synap account is needed to pay for completions.
Before you install
Chat completions are billed per prompt and completion token against a prepaid Synap balance topped up by card or crypto; the other three tools are free. The API key is passed through to the upstream API in the Authorization header, so treat it as a secret. Prompts and completions are stated not to be stored, but they are sent to a third-party service.

Installation

In SourceWeft

  1. Open Synap in the dashboard and add it to a workspace.
  2. 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.linkrra%2Fsynap/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": {
    "synap": {
      "type": "http",
      "url": "https://pool.linkrra.com/mcp"
    }
  }
}

README

Synap MCP server

Synap by Linkrra as a Model Context Protocol server: open models behind one OpenAI-compatible API. Your agent can list the models we serve, read their prices and limits, estimate the cost of a job before running it, and run a chat completion.

There is one server, hosted at https://pool.linkrra.com/mcp (Streamable HTTP). It is the server behind com.linkrra/synap in the official MCP registry.

This repository has two parts:

  • routes.js is the deployed router itself, byte for byte.
  • bin/synap-mcp.js is the stdio transport (npx synap-mcp) for MCP hosts that launch a local command. It sends every message to the hosted server unchanged, so it always exposes the same tools as the hosted server.

Tools

ToolCostKey needed
synap_list_modelsfreeno
synap_get_modelfreeno
synap_estimate_costfreeno
synap_chat_completionbilled per prompt and completion tokenyes

Model ids are the ones synap_list_models returns. Pass synap-v1 and Synap picks the cheapest model that can do the job.

Connect

Hosted (Streamable HTTP), no install needed

json
{  "mcpServers": {    "synap": {      "type": "http",      "url": "https://pool.linkrra.com/mcp",      "headers": { "Authorization": "Bearer YOUR_SYNAP_API_KEY" }    }  }}

Local stdio (Claude Desktop, Cursor, Cline, Windsurf, Zed)

json
{  "mcpServers": {    "synap": {      "command": "npx",      "args": ["-y", "synap-mcp"],      "env": { "SYNAP_API_KEY": "YOUR_SYNAP_API_KEY" }    }  }}

Without a key, the three free tools still work. synap_chat_completion returns an error and nothing is charged.

VariableMeaning
SYNAP_API_KEYYour Synap key, sent as Authorization: Bearer. Get one at https://synap.linkrra.com.
SYNAP_MCP_URLOptional. Overrides the endpoint (default https://pool.linkrra.com/mcp).

Use it from goose

A ready-made goose custom-provider file lives in goose/. Download goose/linkrra.json into ~/.config/goose/custom_providers/, set LINKRRA_API_KEY, and pick Linkrra (Synap) as the provider. Full setup steps and the model table: goose/README.md.

Paying

  • API key (MCP and REST). Top up a Synap account by card or crypto. Each call is billed per token against that balance. MCP always uses this method.
  • x402, no account. An agent with a USDC wallet on Base can pay per call over plain HTTP at POST https://pool.linkrra.com/api/billing/x402/chat/completions. An unpaid request returns 402 with the payment terms. This route is part of the REST API, not an MCP tool. Its settlement is independently verified on PayAPI Market.

Protocol

The hosted server speaks both MCP eras:

  • 2026-07-28 (current): stateless. It implements server/discover and reads the per-request _meta protocol version. It checks that MCP-Protocol-Version, Mcp-Method and Mcp-Name match the request body. Results carry resultType, and list results also carry ttlMs and cacheScope.
  • 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05: the initialize handshake.

The bridge works with both. For a legacy client, it remembers the version agreed during initialize. For a 2026-07-28 client, it copies the _meta version into the HTTP headers that the Streamable HTTP transport requires.

The API behind it

https://pool.linkrra.com/v1 is an OpenAI-compatible API. On every self-hosted model it supports tool calling (tools, tool_choice) and structured outputs (response_format json_object / json_schema). Requests can be streamed or not. Prompts and completions are not stored.

Auth

The server passes your key through and nothing else. The key travels in the standard Authorization: Bearer header, the same way it would on a direct call to /v1/chat/completions. routes.js forwards that header untouched. The server never reads, stores or creates a key.

Run the server standalone

bash
npm install && npm start     # serves :8080/mcp

Develop

bash
npm test     # offline: a local mock checks the bridge's headers for both protocol eras

The stdio bridge needs Node 18 or later and has no dependencies.

License

Apache-2.0

Source: README.md at commit 67ad20b

Tools

4

synap_chat_completion

Run a chat completion on Synap

Send a conversation to a model on Synap, Linkrra's OpenAI-compatible inference API, and get the model's reply. Use this when you need text generated, code written or a question answered by one of the open models Synap serves. This is the only tool here that costs money: it bills prompt and completion tokens to the Synap API key supplied as the Authorization: Bearer header on the MCP connection. With no key it returns an error and nothing is spent; a key with no balance returns insufficient_credits. Call synap_estimate_cost first if the price matters. Returns the standard OpenAI chat.completion JSON (choices[0].message.content holds the reply, usage holds token counts). The call is not streamed and keeps no memory between calls — send the full message history each time.

Parametersmodelrequiredmessagesrequiredmax_tokenstemperature

synap_list_models

List Synap models and prices

List the models Synap serves right now, each with its price per million tokens, context window and what it is good at. Use this to choose a model id before calling synap_chat_completion, or to compare prices. Free, read-only, no API key needed, and safe to call repeatedly; the list is live, so models can appear or go between calls. Returns {"object":"list","count":N,"data":[{id,name,capability,tier,context_tokens,max_output_tokens,pricing,data_policy}]}; pricing is USD per million prompt and completion tokens and is absent for the auto-routing ids ("synap-v1"), which bill at the price of the model they route to. For every field of one model use synap_get_model.

Parametersquery

synap_get_model

Get one Synap model in full

Return the complete catalogue record for one Synap model: pricing, context and output limits, supported parameters, quantisation, data-retention policy and readiness. Use this after synap_list_models when you need details the summary leaves out. Free, read-only and needs no API key. Returns the raw model object, or an error naming the id if Synap does not serve it.

Parametersmodelrequired

synap_estimate_cost

Estimate the cost of a Synap call

Work out what a chat completion would cost on Synap from token counts, using the live price list. Use this before synap_chat_completion when budget matters, or to compare models for a job. Free, read-only, needs no API key and runs no model. Returns {model, prompt_tokens, completion_tokens, prompt_usd, completion_usd, total_usd, pricing}. It is an estimate: the real charge uses the token counts the model reports afterwards. Auto-routing ids such as "synap-v1" have no fixed price and return an error saying so.

Parametersmodelrequiredprompt_tokensrequiredcompletion_tokens

Version history

3
  1. v1.2.0LatestOct 16, 2026
  2. v1.1.0Oct 5, 2026
  3. v1.0.0Sep 16, 2026

Score

100% 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
  • License10 pts