Narrative Engine MCP Server
io.github.jdhart81/narrative-engine
answering
Narrative Engine is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 3 Aug 2026.
Grant, investor & policy narrative generation for conservation work.
Uptime history
41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
328 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add narrative-engine --transport http https://mcp.viridisconservation.com/narrative-engine/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"narrative-engine": {
"url": "https://mcp.viridisconservation.com/narrative-engine/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.narrative-engine]
url = "https://mcp.viridisconservation.com/narrative-engine/mcp".cursor/mcp.json
{
"mcpServers": {
"narrative-engine": {
"url": "https://mcp.viridisconservation.com/narrative-engine/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"narrative-engine": {
"url": "https://mcp.viridisconservation.com/narrative-engine/mcp"
}
}
}Available tools 2
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
describe
describe_agent
Fleet-standard self-description: capabilities, inputs, outputs.
translate
translate_narrative
Translate raw ecological/agent data into a decision-maker-ready narrative.
audience_type: board_member | general_public | grant_funder |
institutional_investor | journalist | policymaker | regulator |
retail_investor | scientist
format_type: academic_paper | executive_summary | grant_proposal |
investor_deck | newsletter | policy_brief | press_release
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.viridisconservation.com/narrative-engine/mcp | streamable-http | answering | 316 ms | 3 min ago |
Narrative Engine — questions
Answers built from our own checks of this server.
What can Narrative Engine do?
It exposes 2 tools, read directly from the server on our last check. Among them: describe_agent, translate_narrative. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Narrative Engine 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 328 ms. The bar chart above shows every period we have measured.
How do I connect Narrative Engine?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Narrative Engine need an API key?
No. Narrative Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Narrative Engine?
It answers our handshake in 328 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Narrative Engine open source?
Yes — written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.