Sylex Search

Universal search engine for AI agents. Discover products, services, and businesses across every category through MCP.

11,000+ entries and growing. Zero cost per query, millisecond responses.

Quick start

Option 1: Remote (no install)

Add to your MCP client config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "sylex-search": {
      "url": "https://mcp-server-production-38c9.up.railway.app/sse"
    }
  }
}

Option 2: Local stdio proxy (this package)

{
  "mcpServers": {
    "sylex-search": {
      "command": "npx",
      "args": ["sylex-search"]
    }
  }
}

Tools

Search & browse

| Tool | Description | |------|-------------| | discover | Search the index. Returns ranked results with fit scores. | | details | Get full product data by ID. | | compare | Side-by-side comparison of 2-5 products. | | categories | Browse all categories and subcategories. | | alternatives | Find similar products to a given one. | | feedback | Report issues or suggest improvements. |

Self-service registration (agents-first)

| Tool | Description | |------|-------------| | register | Register a new product, service, or business. Returns an owner_token for future updates. | | claim | Claim ownership of an existing listing (or recover a lost token) via URL verification. | | update_listing | Update your listing (name, description, category, pricing, etc). Requires owner_token. | | list_mcp | Add MCP connection config so other agents can discover and connect to your server. Requires owner_token. |

How registration works

Everything is designed for agents. No dashboards, no accounts — just MCP tools.

1. Register a new listing

Call register with a name, description, and URL. You get back:

• product_id — your listing's ID in the index
• owner_token — a secret token (like sylex_Kx7m2...) that proves you own this listing

Store the owner_token. You need it every time you update your listing.

2. Claim an existing listing

If your tool is already in the index (from our crawlers), use claim to take ownership:

1. Call claim with just the product_id — you get a verification code and instructions
2. Place the code somewhere you control:
   • GitHub: add it to your repo description or a SYLEX_VERIFY file
   • npm: add "sylexVerify": "<code>" to package.json
   • Website: serve it at /.well-known/sylex-verify
   • DNS: add a _sylex-verify TXT record
3. Call claim again with the product_id + verification_url — we fetch the URL and check for the code
4. You get back an owner_token

3. Update your listing

Call update_listing with your product_id, owner_token, and an updates object. You can change:

• Index fields: name, description, url, category, subcategory, price_model, has_free_tier
• Custom data: any other keys go into the data blob (features, integrations, etc.)

4. Publish your MCP config

Call list_mcp to add connection details so other agents can discover and connect to your MCP server:

SSE:              {"transport": "sse", "url": "https://your-server/sse"}
stdio:            {"transport": "stdio", "command": "npx", "args": ["your-package"]}
streamable-http:  {"transport": "streamable-http", "url": "https://your-server/mcp"}

You can also include "tools" (list of tool names) and "env" (required environment variables).

Lost your token?

Call claim again on your product, even if it's already claimed. Re-verify ownership through any of the methods above, and a new token is issued. The old token stops working immediately.

Example queries

• "react state management" — zustand, redux, mobx, jotai
• "python web framework" — Django, Flask, FastAPI
• "database" — PostgreSQL, MongoDB, MySQL, Redis
• "project management" — Jira, Notion, Asana, Linear

Environment variables

| Variable | Default | Description | |----------|---------|-------------| | SYLEX_SEARCH_URL | Production server | Override the server URL | | PRODUCT_SEARCH_URL | Production server | Legacy alias (backward compat) |

License

AGPL-3.0 — see LICENSE for details.