Algolia Productivity MCP Server

by algolia Your server? Claim it

answering

Algolia Productivity is answering right now. Last checked 13 min ago.

Connect LLM tools to your Algolia account with user-scoped access for internal workflows.

Uptime history 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

27 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Algolia Productivity every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add algolia-productivity --transport http https://mcp.algolia.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.algolia.com/mcp

~/.codex/config.toml

[mcp_servers.algolia-productivity]
url = "https://mcp.algolia.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "algolia-productivity": {
      "url": "https://mcp.algolia.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "algolia-productivity": {
      "type": "http",
      "url": "https://mcp.algolia.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.algolia.com/mcp	streamable-http	needs key	56 ms	13 min ago

Alternatives to Algolia Productivity

same job, measured the same way

Daystruct

by daystruct-api

Find source-package workflows, inspect live prices and evidence, and connect with a scoped key.

26 tools answering

by carhaix

Access Oi Contexts, Workflows, Skills, Guardrails, Connections, and reporting tools.

answering

Wever Labs Agentic Rails

by weverlabs

Agentic rails for complex workflows with receipts, fees, and MCP tool access.

5 tools answering

Accelerators

by s2tconsulting

36 tools for AWS infrastructure, security compliance, AI workflows, and ACI governance.

64 installs/wk local only

Coverctl

by klarlabs-studio

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

local only

Coverctl

by felixgeelhaar

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

local only

Flowra

by flowradev

MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows

answering

Ephemeral

by ephemer

Run AI agent tasks in isolated sandboxes with a cost cap, saved workflows and scoped connections.

19 tools answering

Algolia Productivity — questions

Answers built from our own checks of this server.

Why is there no tool list for Algolia Productivity?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Algolia Productivity working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 27 ms. The bar chart above shows every period we have measured.

How do I connect Algolia Productivity?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Algolia Productivity need an API key?

Yes. Every time we knock, Algolia Productivity answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Algolia Productivity?

It answers our handshake in 27 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.