Loudcode MCP

An official MCP server for Loudcode that allows AI agents to automate 'build in public' posts on X. It reads commits, revenue, and traffic data to draft posts in the user's voice, manages queuing, and tracks metrics, ensuring nothing posts without user review.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Loudcode

You need:keys are created in Account settings

MCP endpoint (Streamable HTTP)

https://loudcode.dev/mcp

Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (6)

draft_post
list_drafts
queue_post
post_metrics
list_ideas
weekly_checkin

6 of 6 have a description · 0 of 6 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 8:06 AM UTC
Passed Official MCP Registry namespace is tied to loudcode.dev · Nov 7, 2026, 6:07 AM UTC
Passed Endpoint is on the registry namespace domain · Nov 7, 2026, 6:07 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Draft build in public posts from commits and revenue
Queue and schedule posts to X
Track post metrics like views and likes
Manage voice and tone for automated content

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: dev.loudcode/loudcode@1.0.0 Project website

Protocol and capabilities

Server: loudcode 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 6 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Loudcode turns what a developer builds into build in public posts for X, in their voice. When the user asks to post about their work, call draft_post with a specific summary of what was built in this session and why it matters. Drafts are saved for review, never posted directly. Only call queue_post when the user asks to queue or schedule.

Tools

6 advertised

draft_post

Advertised by the server during the last successful anonymous check.

Write a build in public post for X about work the user just did, in their own voice (Loudcode knows their product, tone and past posts). Pass a concrete summary of what was built or changed in this session: features, fixes, decisions, numbers, and why it matters to users. Returns the draft (and alternatives). It is saved in Loudcode for the user to review; it is NOT posted.

draft_post input schema

{
  "type": "object",
  "required": [
    "summary"
  ],
  "properties": {
    "format": {
      "enum": [
        "single",
        "thread",
        "long"
      ],
      "type": "string",
      "description": "single (default): one X post. thread: 3 to 5 posts. long: LinkedIn style."
    },
    "summary": {
      "type": "string",
      "description": "What was built or changed, and why it matters. Plain language, specific."
    }
  }
}

list_drafts

Advertised by the server during the last successful anonymous check.

List the user's Loudcode drafts waiting for review, and posts queued to go out, with their ids.

list_drafts input schema

{
  "type": "object",
  "properties": {}
}

queue_post

Advertised by the server during the last successful anonymous check.

Queue a Loudcode draft to post to the user's X account: at their next free posting slot, or at a specific time. Only do this when the user asked to queue or schedule it.

queue_post input schema

{
  "type": "object",
  "required": [
    "draft_id"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "Optional ISO 8601 time with timezone, e.g. 2026-10-14T09:00:00+02:00. Omit for the next free slot."
    },
    "draft_id": {
      "type": "string",
      "description": "The draft's id (from draft_post or list_drafts)."
    }
  }
}

post_metrics

Advertised by the server during the last successful anonymous check.

How the user's recent X posts did: views, likes, replies per post and totals, best post first.

post_metrics input schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "Look back this many days (default 30, max 90)."
    }
  }
}

list_ideas

Advertised by the server during the last successful anonymous check.

Post ideas Loudcode found in the user's product, numbers, posts and repo. Good when they shipped nothing new this week.

list_ideas input schema

{
  "type": "object",
  "properties": {}
}

weekly_checkin

Advertised by the server during the last successful anonymous check.

Do the user's weekly check-in from what you know about their week, and Loudcode plans a week of posts (saved as drafts with suggested times, not posted). Answer each question concretely; leave one empty if you don't know.

weekly_checkin input schema

{
  "type": "object",
  "required": [
    "worked_on"
  ],
  "properties": {
    "next": {
      "type": "string",
      "description": "What's next, or what are they unsure about?"
    },
    "worked_on": {
      "type": "string",
      "description": "What did they work on or ship this week?"
    },
    "hard_or_decision": {
      "type": "string",
      "description": "What was hard, surprising, or a decision they made?"
    },
    "numbers_or_feedback": {
      "type": "string",
      "description": "Any numbers or feedback: users, signups, revenue, messages."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1589 ms
95th percentile latency: 1589 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 8:06 AM UTC · probe · passed · 1589 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http loudcode-mcp https://loudcode.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add loudcode-mcp --url https://loudcode.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable loudcode-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "loudcode-mcp": {
      "url": "https://loudcode.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "loudcode-mcp": {
      "type": "streamableHttp",
      "url": "https://loudcode.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start loudcode-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "loudcode-mcp": {
      "type": "http",
      "url": "https://loudcode.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http loudcode-mcp https://loudcode.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://loudcode.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "loudcode-mcp": {
      "serverUrl": "https://loudcode.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Loudcode MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run Loudcode MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing