Claude Meko connectorWhat Claude can do in your Meko account.
The Claude Meko connector exposes 23 tools. 9 read your memory, saved conversations and knowledge base, 14 write to them or delete from them. Below: what Claude keeps for you, what it can wipe, and the single action the publisher makes it confirm.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes when you work across several assistants
Meko gives Claude somewhere to store what should last beyond one conversation: remembered facts, full exchanges, files and a datapack's knowledge base. You can pick work up in a later session, or pass it to other agents and, through promoted memories, to your team, without re-explaining everything from scratch.
Stop repeating your preferences. Say "remember that this client wants quotes excluding VAT": memory_add stores it, and later memory_search finds it even if you phrase the question differently.
Resume a project that got interrupted. conversation_create opens a thread and conversation_add_message files each exchange in it, with Meko extracting the durable facts afterwards. A later session reads it all back through conversation_get.
Search your team's reference material. knowledgebase_search runs through a datapack's knowledge base, a datapack being Meko's workspace, blending meaning-based and keyword search.
What Claude will not do: promote a memory to the team's shared layer without first showing you which ones and getting your explicit yes, per Meko. Nothing runs in the background either, so for a scheduled sync you want an automation tool, a different job, and the Integrations hub covers it.
The vocabulary in one minute
Five Claude terms to know, plus one from Meko: the datapack, its name for a workspace.
- Connector
- The link you set up once between Claude and an account you own, so Claude can work in it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude takes the ones it needs; the directory sheet lists every one of them.
- Authorization
- Meko's own sign-in screen, where you hand Claude the access it will use. Granted once per person, withdrawn the same way.
- Approval
- The confirmation Claude waits for in the chat before carrying out something that changes your account.
- MCP
- The shared standard behind connectors; it is what lets an assistant like Claude talk to an outside service.
Connect Meko to Claude in three steps
- 01
Find Meko
In Claude, open Customize, then Connectors, and locate Meko in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first so each member can connect.
- 02
Start the connection
Click Connect on its row, then sign in to your Meko account in the window Meko opens itself. If the link ever breaks, use Disconnect and connect again.
- 03
Review the authorization
Read the authorization screen before approving. It is Meko's, not Claude's, and it sets what the access covers. Meko then derives authorization from the signed-in user and the grants that user holds on each datapack.
All 23 tools, grouped by what they do
Meko gives Claude 23 tools: 9 that read your account, 14 that change something in it.
Two groups: what Claude looks up, and what it adds, edits or deletes. Tool names stay exactly as Claude shows them.
- 9 read
- 14 write
What Claude reads (9)
9 toolsNine tools that consult memory, conversations, files and datapacks without altering them.
artifact_get
Retrieves a file stored earlier, by you or by another agent, using its content hash.
conversation_get
Fetches a stored conversation, with its messages if you want them. The agent named has to own that conversation.
memory_search finds them.conversation_list
Lists the conversations held in a datapack, across all of your agents' namespaces.
conversation_get.datapack_describe
Returns information on an existing datapack and, on request, its status.
datapack_list.datapack_list
Lists the datapacks your account can see, in other words your Meko workspaces.
knowledgebase_search
Runs a hybrid search, by meaning and by keyword, across a datapack's knowledge base.
memory_search.memory_get_all
Returns a window of roughly 20 recent memories plus the total count. It is neither a complete list nor an export.
memory_get_by_id
Shows a single memory by its ID.
memory_search is the way in.memory_search
Searches your memories across your agents' namespaces, with ranking that combines meaning, keywords and entities.
memory_get_all returns.What Claude changes (14)
14 toolsFourteen tools that add, edit or delete. Only promoting a memory has a confirmation described by Meko.
artifact_put
Approval: see the rulePlaces a file, whether a report, CSV, PDF or code output, in a datapack so it can be fetched later or shared with other agents.
conversation_add_message
Approval: see the ruleAdds one user and assistant turn to a stored conversation. Meko then extracts the durable facts from the user's message in the background.
conversation_create
Approval: see the ruleSets up a stored conversation container, meant for saving a whole chat or thread rather than a single fact or document. It is the step that comes before logging the messages themselves.
conversation_delete
Approval: see the rulePermanently erases a conversation and all of its messages. The agent named must own that conversation.
conversation_update
Approval: see the ruleChanges a stored conversation's title or metadata.
datapack_create
Approval: see the ruleProvisions a fresh Meko workspace, isolated from the others.
datapack_delete
Approval: see the ruleRemoves an entire datapack. Meko states the operation is irreversible and requires the datapack's explicit ID.
datapack_update
Approval: see the ruleChanges a datapack's name, its description, or its opt-out from conversation search.
memory_add
Approval: see the ruleStores a lasting fact, preference, decision or useful outcome. It is the tool behind any "remember this" request.
memory_delete_all
Approval: see the ruleDeletes an agent's memories, optionally narrowed to one run. Meko frames it as the tool for a full reset or a broad cleanup.
memory_delete_by_id
Approval: see the ruleRemoves one memory identified by its ID. The agent named has to be the one that wrote it.
memory_promote
Asks you firstMoves memories from your private store into the datapack's shared knowledge layer, removing them from your private store. Only datapack owners and maintainers may do this.
memory_update
Approval: see the ruleReplaces the text of an existing memory. The agent named must match the one that originally wrote it.
track_token_usage
Approval: see the ruleRecords a token-usage entry against a conversation trace, so model spend is attributed in Meko's accounting and dashboards.
What Claude checks with you first
By default, Claude pauses and asks for your go-ahead before each action it takes on an account for you. The request shows up in the chat, right when it matters.
Meko adds its own step for promoting memories: a preview of the memories involved, an explanation of team visibility, then your explicit agreement. For the thirteen other writes, no source describes a particular confirmation, so the default rule applies. On Team and Enterprise workspaces, owners decide whether members may let actions through without a prompt, and they can shut off writes for the whole organisation. Claude only acts with the rights your datapacks grant you.
Which plans it's available on
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that information is not published anywhere.
The general rule is sourced: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before members connect. For the live status, the connector's sheet in the official directory is the reference. On Meko's side, what counts is the call quota of your package with them.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: no memory gets saved or cleaned up on a schedule.
Only the publisher documents this connector; neither Claude's help centre nor Anthropic's docs have a page on it. The directory badge is not a security audit, and Anthropic does not guarantee a publisher's tools behave as described. With fourteen write tools, several of them permanent deletions, connect it knowing what it can do. Meko describes some of those deletions as permanent, a conversation with all its messages or an entire datapack, and promoting memories is a one-way move out of your private store.
Need help connecting Meko to Claude?
A person reads every message.