Search1API vs Surface
A side-by-side look at the Search1API and Surface MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SurfaceSearch & Data Extraction · Local subprocess (stdio)Remote MCP (streamable HTTP at https://nova-otter-delta-cloud.grok.me/mcp). Tool preflight_url unwraps short or unknown links (t.co, bit.ly, lnkd.in) before an agent fetches them and returns next: fetch or skip. No page body returned. Usage-priced: Preflight $0.25/1k, Inspect $0.20/1k.74GreatAuth: api key requiredVerdict: choose Search1API for search & data extraction work as a local process; choose Surface for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Search1API when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SEARCH1API_KEY.
SChoose Surface when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SURFACE_API_KEY, SURFACE_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Surface | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 49/100 · Fair | 74/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | SEARCH1API_KEY | SURFACE_API_KEYSURFACE_BASE_URL |
Tools & capabilities
Search1API tools
No tool names declared yet. Check the project README from the listing page.
Surface tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Search1API
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": [
"-y",
"search1api-mcp"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
}
}
}
}
Surface
{
"mcpServers": {
"surface": {
"command": "npx",
"args": [
"-y",
"github:Surface-ops/surface"
],
"env": {
"SURFACE_API_KEY": "YOUR_SURFACE_API_KEY_HERE",
"SURFACE_BASE_URL": "YOUR_SURFACE_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Search1API is categorized under Search & Data Extraction and uses a local stdio subprocess. Surface belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Search1API for search & data extraction work and Surface for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Search1API has no declared pricing — check the project's own site. Surface is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add search1api and surface as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Search1API has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 173 GitHub stars. Surface has 74/100 (Great) with 1 views, 0 installs and 0 GitHub stars.