nana800 runs on your own machine — the client starts it, so there is no endpoint to ping. 396 installs a week from npm.
Build and manage nana800.io no-code workflows: projects, blocks, run history and analytics exports
Today is the operative word: we check nana800 every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-server -e 'MCP_API_KEY=<MCP_API_KEY>' -- npx -y nana800-mcp-server
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"nana800-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}
[mcp_servers.mcp-server]
command = "npx"
args = ["-y", "nana800-mcp-server"]
env = { MCP_API_KEY = "<MCP_API_KEY>" }
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"nana800-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nana800-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}
Put your own value in place of
<MCP_API_KEY> (nana800.io API key. Create or copy it at https://cloud.nana800.io/settings).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
MCP_PROJECT_ID (Default project ID, used when a tool call does not pass project_id), MCP_SCHEME_ID (Default scheme (workflow) ID, used when a tool call does not pass scheme_id), MCP_ANALYTICS_ORG_ID (Default analytics org ID, used when a tool call does not pass org_id. List your orgs with analytics_orgs_list), MCP_API_URL (nana800 API origin), MCP_ANALYTICS_API_URL (nana800 analytics API origin).
Build and run data workflows, analyses, reports and dashboards. Inspect and verify every step.
Build, run and analyse block-diagram simulations: PID, Bode, FFT, optimisation and code export.
timesheet.io MCP server - manage timers, projects, tasks and reports
Manage cross-repository beads work, hive status, and Beadhive workflows through bh-mcp.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Create and manage short links, go links, QR codes, and link-in-bio pages, with click analytics.
Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.
Local-first MCP server for Claude/Codex project wiki and graph workflows
Answers built from our own checks of this server.