Agent
Discoverability

Meko

Shared context for agents that work and learn together.

View in the Claude registry
Integration details

Description

Meko is a data-persistence cloud platform for hybrid teams (AI agents and humans). It gives you a place to keep shared context (agent memory, conversations, and knowledge base docs) without the need for you to stitch it together yourself. We have already done this behind the scenes, so everything just works out of the box with natural language. No knowledge of SQL required. Meko stores "context," which enables sharing across agents and harnesses. Meko stores and enables you to: Save AI conversations and extract facts from them into searchable memory, so work from an earlier session doesn't have to be reprocessed from all the individual pieces of data. Easily upload documents into a hosted knowledge base, so that you don't have to write complex data pre-processing pipelines. Allow resuming your context over time or switching between LLMs and IDEs, so you can pick up where you left off. This is helpful if you run out of tokens, an LLM goes down for a while, or you want to use a different AI provider. Share agent memory and knowledge base documents with other teammates (agents or humans) selectively, so everyone can work together and learn from each other. Store agent traces in a visual portal, so you can see what the agent thought or did during conversations or agentic work. Gain access through a remote MCP endpoint, so that any MCP-capable agent (Claude, Cursor, Codex, and other AI chat apps with MCP) can use it.

Integration type
Connector
Verification status
Verified connector
Platform
Claude
Category
AI

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Enterprise Knowledge Search & AI Context Layer

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Brand
Meko
Access
Account required
First tracked
2026-08-04
Tool count
23
Market
US
Agent DiscoverabilityClaude Discoverability ScoreUpdated daily

The first to track the ChatGPT, Claude, Muse, Grok & Google ecosystems, with the largest database on the core platforms. Tracked daily since .

MekoClaude Connector · Enterprise Knowledge Search & AI Context Layer
Discoverability Score

0/100

Invisible
Category rank

#19of 104

in Enterprise Knowledge Search & AI Context Layer
Picked
0.0/100
Found
1.0/100
Positioned
0.0/100
Is this your product?Improve your Discoverability Score

Category leaderboard

Enterprise Knowledge Search & AI Context Layer

  1. 1Google Drive62
  2. 2Atlassian MCP44
  3. 3Notion37
  4. 4Slack26
  5. 19Meko0
See all 104 competitors

Get alerts for Meko

Get updates when Meko’s Discoverability Score or category rank changes.

#19 of 104ranked by public Discoverability Score
Primary Subcategory
1Google Drive62/100
2Atlassian MCP44/100
3Notion37/100
4Slack26/100
5Linear16/100
19Meko0/100
Tools

23 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

Meko Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve Meko's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Meko alternatives on Claude?

As of 2026-11-02, Meko competes with Google Drive, Atlassian MCP, Notion, Slack, Linear, Superhuman Docs, Microsoft 365, NetDocuments and 95 more in Claude Enterprise Knowledge Search & AI Context Layer, ranked by public Discoverability Score.

Where does Meko rank in Enterprise Knowledge Search & AI Context Layer on Claude?

As of 2026-11-02, Meko ranks #19 of 104 in Claude Enterprise Knowledge Search & AI Context Layer with a Discoverability Score of 0/100 (Invisible).

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.