Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Open AI models through one OpenAI-compatible API: chat, live model list, prices and cost estimates.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http synap https://pool.linkrra.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"synap": {
"url": "https://pool.linkrra.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"synap": {
"type": "http",
"url": "https://pool.linkrra.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The publisher (linkrra.com) is not the repo owner (jimmyplup); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.| Tool | Cost | Key needed |
|---|---|---|
synap_list_models | free | no |
synap_get_model | free | no |
synap_estimate_cost | free | no |
synap_chat_completion | billed per prompt and completion token | yes |
Model ids are the ones synap_list_models returns. Pass synap-v1 and Synap picks the cheapest model that can do the job.
{
"mcpServers": { "synap": { "type": "http", "url": "https://pool.linkrra.com/mcp", "headers": { "Authorization": "Bearer YOUR_SYNAP_API_KEY" } } } }
{
"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.
| Variable | Meaning |
|---|---|
SYNAP_API_KEY | Your Synap key, sent as Authorization: Bearer. Get one at https://synap.linkrra.com. |
SYNAP_MCP_URL | Optional. Overrides the endpoint (default https://pool.linkrra.com/mcp). |
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.
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.The hosted server speaks both MCP eras:
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.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.
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.
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.
npm install && npm start # serves :8080/mcp
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.
Apache-2.0