Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Run Together AI chat, embeddings and images; manage fine-tunes, batches and endpoints.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://together-ai.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http together-ai https://together-ai.usefulapi.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"together-ai": {
"url": "https://together-ai.usefulapi.io/mcp"
}
}
}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": {
"together-ai": {
"type": "http",
"url": "https://together-ai.usefulapi.io/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://together-ai.usefulapi.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
together_whoamiIdentify the API key: its organization, project and project slug. The project slug forms the ` / ` model name for dedicated-endpoint inference. A cheap way to confirm the key works. Together: GET /whoami.
together_list_modelsList Together's models with type (chat, language, code, image, embedding, moderation, rerank), context length, organization, license and per-token pricing. Together: GET /models.
together_list_filesList uploaded data files (fine-tune, eval and batch-api inputs, plus job outputs) with size, type, purpose and validation status. Together: GET /files.
together_get_fileFetch one file's metadata, including its processing_status and validation_report (why a fine-tune training file was rejected). Together: GET /files/{id}.
together_list_fine_tunesList fine-tuning jobs with status, base model, output model name and training settings. Together: GET /fine-tunes.
together_get_fine_tuneFetch one fine-tuning job: status, progress, hyperparameters, token counts, cost and the output model name. Together: GET /fine-tunes/{id}.
together_list_fine_tune_eventsList the event log of one fine-tuning job (queued, started, checkpoint saved, epoch completed, errors). The first place to look when a job failed. Together: GET /fine-tunes/{id}/events.
together_list_batchesList batch inference jobs with status, progress, model and input/output/error file ids. Together: GET /batches.
together_get_batchFetch one batch job: status (VALIDATING, IN_PROGRESS, COMPLETED, FAILED, EXPIRED, CANCELLED), progress, and the output_file_id / error_file_id once done. Together: GET /batches/{id}.
together_list_endpointsList endpoints with model, owner and state (PENDING, STARTING, STARTED, STOPPING, STOPPED, ERROR). Use mine=true and type=dedicated to see what is running on your account and billing by the minute. Together: GET /endpoints.
together_get_endpointFetch one dedicated endpoint: state, model, hardware, autoscaling bounds and display name. Together: GET /endpoints/{endpointId}.
together_list_hardwareList hardware configurations for dedicated endpoints with GPU type/count/memory and price in cents per minute. Pass a model to get only compatible configurations with live availability. Together: GET /hardware.
together_list_evaluationsList LLM-as-a-judge evaluation jobs (classify, score, compare) with status, parameters and results once completed. Together: GET /evaluation.
together_chat_completionRun a chat completion on a Together model (billed per token). Non-streaming. For a dedicated endpoint pass its ` / ` as the model. Together: POST /chat/completions.
together_create_embeddingsGenerate vector embeddings for one or more texts (billed per token). Together: POST /embeddings.
together_generate_imageGenerate images from a prompt (billed per image/megapixel). Returns image URLs by default rather than base64, to keep responses small. Together: POST /images/generations.
together_create_fine_tuneStart a fine-tuning job on an uploaded training file (billed per token processed). Stop it with together_cancel_fine_tune. Together: POST /fine-tunes.
together_cancel_fine_tuneCancel a running fine-tuning job. Cannot be resumed, but a new job can continue from its last checkpoint via from_checkpoint. Together: POST /fine-tunes/{id}/cancel.
together_create_batchStart an asynchronous batch job over an uploaded JSONL input file (purpose batch-api), at a discount to real-time inference. Together: POST /batches.
together_cancel_batchCancel a batch job that has not finished. Together: POST /batches/{id}/cancel.
together_create_endpointDeploy a model on dedicated GPUs. The endpoint STARTS AUTOMATICALLY and bills per minute of uptime until stopped — set inactive_timeout to auto-stop it, and use together_list_hardware for valid hardware ids. Together: POST /endpoints.
together_start_endpointStart a stopped dedicated endpoint. It bills per minute of uptime until stopped. Reversible with together_stop_endpoint. Together: PATCH /endpoints/{endpointId} with state=STARTED.
together_stop_endpointStop a running dedicated endpoint, which stops its per-minute billing. Requests to it fail until it is started again. Together: PATCH /endpoints/{endpointId} with state=STOPPED.
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 registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 23 ms (HTTP 200)
No sign-in needed
Read 23 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.35.3) reached the registry yesterday.
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.
Use Together AI from Claude, Cursor, or any MCP client — list models, run chat, embeddings and image generation, and manage fine-tuning jobs, batches and dedicated endpoints. Hosted, no local install: connect with your own Together AI credentials.
Live endpoint: https://together-ai.usefulapi.io/mcp · Homepage: https://usefulapi.io/together-ai
https://together-ai.usefulapi.io/mcp.claude mcp add --transport http together-ai https://together-ai.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "together-ai": { "url": "https://together-ai.usefulapi.io/mcp" } } }
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Together AI credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/together-ai/
On first connect you'll provide your Together AI API key (Settings → API Keys). They're validated, stored per-user, and scoped to you — no keys in config files.
| Tool | Type | What it does |
|---|---|---|
together_whoami | read | Who am I |
together_list_models | read | List models |
together_list_files | read | List files |
together_get_file | read | Get one file |
together_list_fine_tunes | read | List fine-tuning jobs |
together_get_fine_tune | read | Get one fine-tuning job |
together_list_fine_tune_events | read | List a fine-tuning job's events |
together_list_batches | read | List batch jobs |
together_get_batch | read | Get one batch job |
together_list_endpoints | read | List endpoints |
together_get_endpoint | read | Get one endpoint |
together_list_hardware | read | List hardware |
together_list_evaluations | read | List evaluation jobs |
together_chat_completion | write | Chat completion |
together_create_embeddings | write | Create embeddings |
together_generate_image | write | Generate an image |
together_create_fine_tune | write | Create a fine-tuning job |
together_cancel_fine_tune | write | Cancel a fine-tuning job |
together_create_batch | write | Create a batch job |
together_cancel_batch | write | Cancel a batch job |
together_create_endpoint | write | Create a dedicated endpoint |
together_start_endpoint | write | Start a dedicated endpoint |
together_stop_endpoint | write | Stop a dedicated endpoint |
together_ai_usage_status | meta | Usage status (free-tier meter) |
together_ai_request_feature | meta | Request a missing feature |
together_ai_upgrade | meta | Upgrade to Pro or Pro+ |
together_ai_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this server only. Subscribe with together_ai_upgrade (it returns a Stripe Checkout link). Cancel any time with together_ai_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running together_ai_upgrade before then undoes the cancel. Or write to support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by Together AI.