Hosted MCP server/Productivity

Retrievr.io MCP server

Hosted at retrievr.io·Streamable HTTP

Retrievr.io adds retrieval to an agent through MCP. The provider’s install flow mints a key into ~/.config/retrievr/credentials without printing it, installs a local mcp.mjs server, and documents the hosted option: https://retrievr.io/mcp with an Authorization: Bearer key. The endpoint answered an invalid-key challenge on 16 November 2026. The flow is the supported setup; the directory’s earlier one-click installers were not provider-documented.

retrievr.io Streamable HTTP API key (Bearer) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Agent developers adding document retrieval without building a RAG stack.

  • Add retrieval to an agent workflow.
  • Retrieve documents for an agent task.
  • Connect with a Bearer key or the local mcp.mjs server.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Retrievr connect flow

Run the provider connect flow to mint the key without printing it, then add https://retrievr.io/mcp with Authorization: Bearer as the hosted path (or use the local mcp.mjs server the flow installs).

  1. Run the connect flow

    The provider script performs the key exchange and writes the key to ~/.config/retrievr/credentials without printing it.

    curl -fsSL https://retrievr.io/connect -o /tmp/retrievr-connect.sh
  2. Add the hosted MCP server

    Add https://retrievr.io/mcp with Authorization: Bearer <key>, or use the local ~/.config/retrievr/mcp.mjs server the flow installs.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://retrievr.io/mcp
Host
retrievr.io · /mcp
Transport
Streamable HTTP
Authentication
API key (Bearer)
Server name
retrievr-io
Listing type
Community or directory listing

The installer uses the server name retrievr-io. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that retrievr-io appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Add retrieval to an agent workflow. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Retrievr.io documentationhttps://retrievr.io/install