Vectara MCP server

What the model can do

Vectara retrieval platform: the account's corpora with their size, semantic search across one or more corpora returning the best-matching passages with scores, document lists and contents, background jobs and agents. When you ask, can add a document to a corpus, merge or replace a document's metadata, delete documents by id, create, rename, disable or enable a corpus, empty a corpus, and delete a corpus.

Reads

• vectara_list_corporaVectara corpora this key can see: key, name, description, enabled, encoder, document count and creation date.
• vectara_get_corpusOne Vectara corpus: name, description, enabled, encoder, filterable metadata fields, and usage (documents, parts, bytes used of the maximum).
• vectara_searchSemantic search over one or more Vectara corpora: the best-matching passages with their score, corpus, document id and the document's metadata.
• vectara_list_documentsDocuments in a Vectara corpus: id, metadata, part, table and image counts and bytes used.
• vectara_get_documentOne Vectara document: metadata, counts, and the text of its first parts (up to 10, each cut to 600 characters).
• vectara_list_jobsVectara background jobs (bulk deletes, metadata updates, index rebuilds): type, state, corpora, when created and completed, and progress.
• vectara_list_agentsVectara agents: key, name, description, model, whether enabled, and when created and changed.

Acts, when you ask

These change something in Vectara. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• vectara_create_documentAdds a text document to a Vectara corpus under a new id, with a title, sections and metadata…
• vectara_update_document_metadataMerges metadata into a Vectara document: the keys given are added or overwritten, the rest are kept.
• vectara_replace_document_metadataReplaces all of a Vectara document's metadata with the object given; keys not in it are removed.
• vectara_delete_documentPermanently deletes one document from a Vectara corpus; it stops appearing in searches.
• vectara_delete_documentsPermanently deletes the named documents (up to 100 ids) from one Vectara corpus as a background job; vectara_list_jobs shows its progress.
• vectara_create_corpusCreates an empty Vectara corpus with the given key, name and description, ready for documents.
• vectara_update_corpusRenames or re-describes a Vectara corpus, or disables it (taking it offline for search and indexing without deleting it) or enables it again.
• vectara_reset_corpusEmpties a Vectara corpus, permanently removing every document and its data while keeping the corpus and its settings.
• vectara_delete_corpusPermanently deletes a Vectara corpus and all its documents and data; its key is released.

Connect it

First connect Vectara on Dashboard → Connections, then add Memtro to your client once. The Vectara tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Vectara connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What does the policies corpus say about refunds?
• › Which corpora are closest to their storage maximum?
• › Which documents in the contracts corpus have the status archived?
• › Has the bulk delete from last night finished?
• › Disable the old support corpus.

Questions

Is this an official Vectara MCP server?

No. It is Memtro's MCP server with Memtro's Vectara connector behind it: the connector reads Vectara through its API with the credentials you connect on Dashboard → Connections, and Vectara publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Vectara?

Only when you ask, and only what it has been granted: add a text document to a corpus; merge new metadata into a document; replace a document's metadata; delete a document (permanent); delete up to 100 named documents (permanent, runs as a background job); create a corpus; rename, describe, disable or enable a corpus; empty a corpus of every document (permanent); delete a corpus and all its data (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server