Recala

What Recala does

Recala provides MCP access to workflows around articles, topics, and search visibility. Agents can use the connection to manage these areas within a Recala company account. Publishing is governed by human approval, so agent-assisted content work does not imply unattended publication.

The server is intended for teams using Recala as part of their content or search-visibility process. Its scope is company-specific: authentication grants access to the company associated with the signed-in Recala account rather than exposing a general, cross-company workspace.

How it works

Recala is available as a hosted Streamable HTTP MCP endpoint:

https://recala-production.up.railway.app/mcp

An MCP client connects to that URL, then authenticates through Recala OAuth. After sign-in, the connection can operate within the authorized company scope. The MCP interface gives an agent access to Recala operations for articles, topics, search visibility, and publishing workflows.

Because the endpoint is hosted, clients connect to Recala over the network rather than launching a local MCP process. The available connection details are therefore centered on the endpoint URL and OAuth sign-in.

Setup and configuration

1. Add the hosted Streamable HTTP endpoint to an MCP-compatible client:

   https://recala-production.up.railway.app/mcp

2. Start the connection and complete Recala OAuth when prompted.

3. Confirm that the authenticated Recala account belongs to the company whose articles, topics, and search-visibility data the agent should manage.

4. Use the available MCP operations for content and visibility work, keeping human approval in the publishing loop.

The server is also listed in the Official MCP Registry under io.github.annamau/recala. No local package installation or environment-variable configuration is required for the hosted endpoint described here.

Tools and capabilities

• Manage Recala articles.
• Manage Recala topics.
• Work with search visibility.
• Support human-approved publishing.
• Authenticate through Recala OAuth.
• Restrict access to the authorized company.

Limitations and notes

Publishing is human-approved, so an agent should be treated as part of the preparation and management workflow rather than as an autonomous publisher. Access is limited by the company associated with the Recala OAuth session. The documented deployment is hosted at Recala’s Streamable HTTP URL, which means client network access to that endpoint is required.