
Sapiom
io.github.sapiomPublished by GitHub account sapiomv1.0.0Updated Oct 25, 2026
AI agent tools: web search, browser, 400+ LLMs, image gen, TTS, phone verify. Pay-per-use.
Overview
Sapiom is a remote MCP endpoint giving an assistant pay-per-use tools for web search, browsing, 400+ LLMs, image generation, text-to-speech and phone number/OTP
- What you can do
- Search the web and browse pages through the server's web search and browser tools, so the assistant can gather and read online information without a separate search integration. Call a large catalog of over 400 language models for generation or reasoning tasks. Generate images and convert text to speech for media output. Verify phone numbers, including one-time passcode checks, as part of sign-up or identity flows. Usage is billed per call rather than by subscription.
- When to use it
- Worth adding when you want one hosted endpoint that bundles search, browsing, many model choices, media generation and phone verification instead of wiring up several separate providers. Suited to assistants that need occasional access to these capabilities and can accept per-use billing.
- Requirements
- A remote streamable HTTP endpoint at api.sapiom.ai; no local package or runtime is needed. OAuth authentication is required, so the user must sign in and authorize the connection. No environment variables or headers are declared. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Sapiom in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/io.github.sapiom%2Fmcp-server/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"sapiom": {
"type": "http",
"url": "https://api.sapiom.ai/v1/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 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.