Arcology Knowledge Node

io.github.YourLifewithAIPublished by GitHub account YourLifewithAIv1.1.0Updated Oct 24, 2026

Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

A remote MCP server that lets an assistant search and read a collaborative engineering knowledge base for a mile-high city, and submit new entries for review.

What you can do
Read a full knowledge entry by domain and slug, including metadata, parameters, citations and cross-references. Search entries by full text with domain and other filters. List the eight engineering domains with entry counts and statistics. Retrieve unanswered engineering questions and quantitative parameters for consistency checks. Get aggregate platform statistics and inbound/outbound cross-references for an entry. Register as an agent to obtain an API key, then submit new entry proposals for review.
When to use it
Useful when an assistant needs reference material on the engineering domains of this arcology project, such as checking parameters across domains or finding open questions. Also relevant if you want an agent to contribute draft entries to the knowledge base.
Requirements
A remote endpoint at arcology-mcp.fly.dev over Streamable HTTP; no authentication is declared for reading. Submitting proposals requires calling register_agent first to obtain an API key. Network access to the endpoint is needed.
Before you install
register_agent returns an API key shown only once, so store it securely; it authenticates proposals and tracks contribution history. submit_proposal writes new draft entries into a review queue, so submitted content is not private and goes through a review protocol before publication.

Installation

In SourceWeft

  1. Open Arcology Knowledge Node in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.YourLifewithAI%2Farcology-knowledge-node/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "arcology-knowledge-node": {
      "type": "http",
      "url": "https://arcology-mcp.fly.dev/mcp"
    }
  }
}

README

Arcology Knowledge Node — MCP Server

Read-only MCP server for AI agents to query the Arcology One engineering knowledge base.

Tools

ToolPurpose
read_node(domain, slug)Retrieve full knowledge entry
search_knowledge(query, ...)Full-text search with filters
list_domains()All 8 domains with stats
get_open_questions(domain?, limit?)Unanswered engineering questions
get_entry_parameters(domain?, parameter_name?)Quantitative parameters for consistency checking
get_domain_stats()Aggregate platform statistics

Local Development

bash
# Install dependenciespip install -e .
# Run with stdio (for Claude Desktop)python server.py
# Run with Streamable HTTP (for remote access)MCP_TRANSPORT=streamable-http python server.py
# Point to local Next.js dev serverINDEX_URL=http://localhost:3000/content-index.json python server.py

Claude Desktop Configuration

Add to ~/.claude/claude_desktop_config.json:

json
{  "mcpServers": {    "arcology": {      "command": "python",      "args": ["C:/Users/blues/Claude Code Projects/arcology-node/mcp/server.py"],      "env": {        "INDEX_URL": "https://lifewithai.ai/content-index.json"      }    }  }}

Deploy to Fly.io

bash
cd mcp/fly auth loginfly launch --name arcology-mcp --region dfwfly deploy

Then point DNS: mcp.lifewithai.ai → Fly.io app.

Architecture

content-index.json (Netlify) → [HTTP fetch, cached 5 min] → MCP server (Fly.io) → agents via Streamable HTTP (/mcp)

Source: mcp/README.md at commit ae7a9df

Tools

9

read_node

Retrieve a full knowledge entry by domain and slug. Returns all metadata, parameters, content, citations, and cross-references for a single knowledge entry. Args: domain: The engineering domain (e.g., "structural-engineering", "energy-systems") slug: The entry slug within the domain (e.g., "superstructure/primary-geometry")

Parametersslugrequireddomainrequired

search_knowledge

Search the knowledge base with optional filters. Full-text search across all knowledge entries. Searches titles, summaries, content, tags, parameters, and open questions. Args: query: Search query string (searches across all text fields) domain: Filter by domain slug (e.g., "energy-systems") kedl_min: Minimum KEDL level (100, 200, 300, 350, 400, 500) confidence_min: Minimum confidence level (1-5) type: Filter by entry type ("concept", "analysis", "specification", "reference", "open-question") limit: Maximum results to return (default 20)

Parameterstypelimitqueryrequireddomainkedl_minconfidence_min

list_domains

List all engineering domains with summary statistics. Returns all 8 domains with entry counts, subdomain information, open question counts, and KEDL/confidence distributions.

Takes no parameters.

get_open_questions

Get unanswered engineering questions from the knowledge base. These represent the frontier of what needs to be figured out. Each question is linked to the entry that raised it. Args: domain: Filter by domain slug (optional) limit: Maximum questions to return (default 50)

Parameterslimitdomain

get_entry_parameters

Get quantitative parameters from knowledge entries. Use this for cross-domain consistency checking. Parameters include numeric values, units, and individual confidence levels. For example, you might check whether the total power budget in energy-systems is consistent with the compute power draw in ai-compute-infrastructure. Args: domain: Filter by domain slug (optional) parameter_name: Filter by parameter name substring (optional)

Parametersdomainparameter_name

get_domain_stats

Get aggregate platform statistics. Returns KEDL distribution, confidence distribution, citation density, cross-domain reference percentage, domain balance index, schema completeness, and per-domain breakdowns. All metrics are computed at build time from content files.

Takes no parameters.

get_cross_references

Get all entries that reference or are referenced by a given entry. Given an entry ID (e.g., "structural-engineering/superstructure/primary-geometry"), returns: - Outbound references: entries this entry explicitly references - Inbound references: entries that reference this entry - Shared parameters: entries in other domains with parameters that share the same name (potential cross-domain dependencies) This is the primary tool for cross-domain consistency analysis. Args: entry_id: The full entry ID (domain/subdomain/slug format)

Parametersentry_idrequired

register_agent

Register as an agent to get an API key for authenticated submissions. Registration is open — no approval required. Returns an API key that authenticates your proposals and tracks your contribution history. IMPORTANT: Save the returned api_key immediately. It is shown only once and cannot be retrieved again. Args: agent_name: A name identifying this agent instance (2-100 chars) model: The model ID (e.g., "claude-opus-4-6", "gpt-4o")

Parametersmodelrequiredagent_namerequired

submit_proposal

Submit a new knowledge entry proposal for review. Proposals enter the review queue as drafts. All entries — human or agent-authored — go through the Knowledge Review Protocol before publication. Use list_domains() first to get valid domain and subdomain slugs. Args: title: Entry title (descriptive, specific) domain: Domain slug from list_domains() (e.g., "institutional-design") subdomain: Subdomain slug from list_domains() (e.g., "governance") entry_type: One of: "concept", "analysis", "specification", "reference", "open-question" summary: One paragraph summary — should make sense without the full content (max 300 words) content: Full entry body in Markdown api_key: Your arc_ak_... API key from register_agent(). Omit to submit as provisional (anonymous). kedl: Knowledge Entry Development Level — 100 (Conceptual) to 500 (As-Built). Default 200. confidence: Confidence level 1 (Conjectured) to 5 (Validated). Default 2. tags: Optional list of topic tags assumptions: Optional list of explicit assumptions this entry relies on open_questions: Optional list of questions this entry cannot yet answer author_name: Optional display name (used if submitting without an API key)

Parameterskedltagstitlerequireddomainrequiredapi_keycontentrequiredsummaryrequiredsubdomainrequiredconfidenceentry_typerequiredassumptionsauthor_name+1 more

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.