Sofya

co.sofyaPublished by sofya.coOfficial publisherv1.28.0Updated Oct 29, 2026

Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Sofya gives an AI assistant web search, page fetching, AI extraction and cited deep research, returning clean markdown and synthesized answers.

What you can do
  • Search the web and get extracted page content, with news topic, domain filters, freshness and an optional AI-synthesized answer
  • Fetch up to 10 URLs as clean markdown, including PDF, DOCX, XLSX, PPTX and EPUB files
  • Extract specific information from a page using AI
  • Run deep research: split a question into sub-queries, read many sources in parallel and synthesize a cited report
  • Check the account's remaining credits and get a payment link for a top-up (hosted server only)
When to use it
Useful when an assistant needs current web information rather than snippets: reading and summarizing documents behind URLs, pulling structured facts out of a page, or producing a multi-source cited report on a topic.
Requirements
Remote endpoint at mcp.sofya.co over streamable HTTP, or a local build run over stdio with Node.js 18+. A Sofya account signed in via OAuth, or a Sofya API key sent as an Authorization Bearer token (hosted) or set as SOFYA_API_KEY (local). Network access to the Sofya API.
Before you install
Usage is metered in credits: search costs 1-2 credits (plus 2 for an answer), fetch 1 credit per URL, extract 10 and research 50, so heavy use spends money. Eligible GitHub accounts get free monthly credits; others pay as they go. The API key is a secret and should be kept out of shared configs. Queries and fetched URLs are sent to Sofya's service.

Installation

In SourceWeft

  1. Open Sofya in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/co.sofya%2Fsofya/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sofya": {
      "type": "http",
      "url": "https://mcp.sofya.co/mcp"
    }
  }
}

README

sofya-mcp

[Listed on mcpservers.org]

MCP server for Sofya - web search, fetch, extract, and deep research for AI agents, exposed over the Model Context Protocol.

Use it either way:

  • Hosted (no install): connect your client to https://mcp.sofya.co/mcp (streamable HTTP). Sign in with OAuth, or send your API key as a Bearer token. This is the server listed in the MCP registry as co.sofya/sofya.
  • Local: build this repo and run it over stdio. It is a thin wrapper around the Sofya REST API with the four core tools.

Eligible GitHub accounts (a year or older) get free monthly credits; everyone else pays as they go.

Tools

ToolWhat it doesCost
searchSearch the web and get extracted page content (not just snippets). Supports news topic, domain filters, freshness, and an optional AI-synthesized answer.1-2 credits (+2 for include_answer)
fetchFetch up to 10 URLs as clean markdown. Also handles PDF, DOCX, XLSX, PPTX, EPUB, and more.1 credit / URL
extractFetch a page and pull specific information from it using AI.10 credits
researchDecompose a question into sub-queries, read many sources in parallel, and synthesize a cited report.50 credits
get_balanceShow the account's remaining credits. Hosted server only.free
buy_creditsReturn a payment link for a credit top-up. It does not charge anything. Hosted server only.free

search, fetch, extract, research and get_balance are read-only.

Hosted server (VS Code / Copilot and others)

Point your client at the hosted endpoint. Clients with OAuth support (Claude, VS Code, Cursor, Cline and others) only need the URL and will ask you to sign in. To use an API key instead, get one at sofya.co (keys look like sofya_live_...) and send it as a Bearer token:

VS Code / GitHub Copilot (.vscode/mcp.json):

json
{  "servers": {    "sofya": {      "type": "http",      "url": "https://mcp.sofya.co/mcp",      "headers": { "Authorization": "Bearer sofya_live_..." }    }  }}

Claude Code, as a plugin (signs in with OAuth; plugin files in plugins/sofya):

bash
/plugin install sofya --marketplace sofya-co/sofya-mcp

Claude Code, with an API key:

bash
claude mcp add --transport http sofya https://mcp.sofya.co/mcp --header "Authorization: Bearer sofya_live_..."

Cursor (~/.cursor/mcp.json):

json
{  "mcpServers": {    "sofya": {      "url": "https://mcp.sofya.co/mcp",      "headers": { "Authorization": "Bearer sofya_live_..." }    }  }}

Cline:

bash
cline mcp install sofya --transport http https://mcp.sofya.co/mcp

Or in cline_mcp_settings.json:

json
{  "mcpServers": {    "sofya": {      "type": "streamableHttp",      "url": "https://mcp.sofya.co/mcp",      "headers": { "Authorization": "Bearer sofya_live_..." }    }  }}

Then ask your agent things like "search for the latest Node.js LTS release notes", "fetch this PDF and summarize it", or "research how the EU AI Act treats open-weight models". Full API docs: sofya.co/docs.

Local server

Prerequisites

  • Node.js 18+
  • A Sofya API key - get one at sofya.co (keys look like sofya_live_...)

Build

bash
git clone https://github.com/sofya-co/sofya-mcp.gitcd sofya-mcpnpm install          # also builds to build/index.js

Check it starts:

bash
SOFYA_API_KEY=sofya_live_... node build/index.js

In the examples below, replace /path/to/sofya-mcp with the folder you cloned.

Configuration

Claude Code
bash
claude mcp add sofya --env SOFYA_API_KEY=sofya_live_... -- node /path/to/sofya-mcp/build/index.js
Claude Desktop / Cursor / Windsurf / VS Code

Add this to your MCP config (e.g. claude_desktop_config.json, or .cursor/mcp.json):

json
{  "mcpServers": {    "sofya": {      "command": "node",      "args": ["/path/to/sofya-mcp/build/index.js"],      "env": {        "SOFYA_API_KEY": "sofya_live_..."      }    }  }}
Codex

Add it with the Codex CLI:

bash
codex mcp add sofya --env SOFYA_API_KEY=sofya_live_... -- node /path/to/sofya-mcp/build/index.js

Or edit ~/.codex/config.toml directly. Note Codex puts environment variables in a nested [mcp_servers.<name>.env] table:

toml
[mcp_servers.sofya]command = "node"args = ["/path/to/sofya-mcp/build/index.js"]
[mcp_servers.sofya.env]SOFYA_API_KEY = "sofya_live_..."

Then run /mcp inside Codex to confirm the server is connected.

Environment variables

VariableRequiredDefaultDescription
SOFYA_API_KEYyes-Your Sofya API key (sofya_live_...; older ay_live_... keys still work).
SOFYA_BASE_URLnohttps://sofya.coOverride the Sofya API base URL.

CLI flags --api-key and --base-url take precedence over the env vars. Run node build/index.js --list-tools to print the tool schemas, or --help for options.

Development

bash
npm run build        # compile TypeScript to build/npm run watch        # recompile on changenpm run inspector    # debug with @modelcontextprotocol/inspector

The server is a single file, src/index.ts. Tool definitions mirror Sofya's hosted MCP server exactly (same names, parameters, and defaults).

License

MIT - see LICENSE.

Source: README.md at commit 9403747

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.28.0LatestOct 29, 2026
  2. v1.27.1Oct 5, 2026
  3. v1.27.0Sep 16, 2026

Score

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