General Tools
elephant.md
Search and retrieve documents from elephant.md using full-text, semantic, and natural language search.
ENDPOINT 1
https://elephant.md/mcp
MCP server metadata
- Name
- elephant
- Version
- 1.0.0
Elephant is your searchable markdown brain — long-term memory for an AI agent, organized into documents and collections across many topics. SCOPED BY DEFAULT. With an auth token, every search defaults to YOUR library: documents and collections you own or have bookmarked (bookmarking a collection puts its documents — present and future — in your scope). Pass scope:"public" to search the whole public corpus instead. Without a token you search public documents only. The server NEVER silently widens to public — if your library has nothing relevant it says so and suggests scope:"public", so you stay in control. START HERE → ROUTE → READ. 1. Call `overview` first (pass your token) for a cheap table of contents of your collections — names, summaries, sizes, freshness. A few hundred tokens. 2. Then call `get_context(query, tokenBudget)` — it searches your scope, returns ranked summary cards, AND inlines the top documents' full content up to your token budget, so you get usable context in ONE round trip. It also returns the most relevant collections to drill into and `candidates` (cards it didn't inline) you can fetch later. 3. Responses are summaries-first: cards (tens of tokens each) by default; full content only on explicit fetch, always within a maxTokens budget. NAVIGATION TOOLS: - `overview` — your starting map (your + bookmarked collections grouped by scope, plus totals). - `get_context` — the one-call router: route-then-read within a token budget. Use this for "bring me context about X". - `find_collections` — rank your COLLECTIONS by a query, then drill into the right one. - `search_collection` — full-text + semantic search WITHIN one collection. - `search` / `discover` — document search across your scope (or scope:"public"); `discover` is natural-language/semantic. - `fetch` — one document's full markdown; pass `section` for a single heading or `maxTokens` to cap size. - `fetch_collection` — a whole collection token-efficiently (summaries, or full bodies within maxTokens). - `bookmark` — save a document, or a collection (= subscribe: its documents join your scope automatically). Prefer `get_context` for open-ended context gathering; use the discrete tools when you already know which collection or document you want. Authenticated tools take a `token` parameter (your session token from the elephant.md settings page).
Known tools 20
discoverDiscover documents using natural language semantic search (powered by embeddings).
Inferred read-onlyget_contextRoute-then-read in ONE call: searches your context for `query`, returns ranked summary cards, and inlines the top documents' full content up to `tokenBudget` so you get usable context in a single round trip.
Inferred read-onlyfind_collectionsFind the most relevant COLLECTIONS for a query — route to the right collection, then `search_collection` or `fetch_collection` it.
Inferred read-onlysearch_collectionSearch WITHIN one collection (full-text + semantic, scope-gated to that collection's members).
Inferred read-onlycreate_burn_linkMint a self-destructing share link (burn link) for ephemeral content.
Inferred read-onlyoverviewYour starting map: a cheap table of contents of the context available to you.
Inferred read-onlylist_collectionsList your collections — those you own plus collections you've bookmarked.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.elephant]
url = "https://elephant.md/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"elephant": {
"type": "http",
"url": "https://elephant.md/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: elephant
Remote MCP URL: https://elephant.md/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"elephant": {
"url": "https://elephant.md/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"elephant": {
"type": "http",
"url": "https://elephant.md/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "elephant",
"transport": "streamable-http",
"url": "https://elephant.md/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for elephant.md was fetched 2026-08-03T23:44:36.839Z and is being refreshed.
elephant.md is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.