# TakoCode [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/takocode-chimera/takocode-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/takocode

## Description
Build, preview and publish full-stack web apps with TakoCode's hosted coding agent.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "takocode": {
    "url": "https://takocode.com/api/mcp"
  }
}
```

## Documentation

## What the TakoCode MCP server does

The TakoCode MCP server gives an MCP-capable assistant access to TakoCode’s hosted app-building platform. The assistant can create a project, send a build goal to the hosted coding agent, monitor the resulting work, and retrieve project outputs. Supported outputs include a temporary preview link, a signed source-code download, a GitHub export, and deployment to a permanent public URL.

The server also covers account and commercial workflow tasks. Assistants can read membership, wallet, spending, and available-turn information; save user preferences; provide checkout links for wallet credits; search domain availability; and start domain purchases or attach an existing domain. Human approval remains part of payment and publishing flows.

## How it works

TakoCode MCP server connections use the remote endpoint `https://takocode.com/api/mcp` over Streamable HTTP. Authentication uses OAuth 2.0 with dynamic client registration, so the user signs in with a TakoCode account rather than configuring a local token or running repository code.

Build work is asynchronous. A client sends one defined goal with `start_turn`, then polls it with `check_turn`. This design allows a build to continue even if the MCP client disconnects or reaches a timeout. A completed turn can report a final message, cost, files, and an optional screenshot.

Each tool includes MCP read-only or destructive annotations so compatible clients can decide when to request confirmation. Wallet top-ups and domain purchases return Stripe checkout links for the human user; the assistant cannot complete those charges itself. Publishing requires explicit user approval, subject to server-enforced autonomy preferences and any configured monthly budget cap.

## Setup and configuration

There is no local installation. The repository contains documentation and listing metadata, while the implementation runs on TakoCode infrastructure. In Claude, add a custom connector under Settings, paste the remote endpoint, and complete the sign-in prompt. Other MCP clients can connect using the same remote Streamable HTTP endpoint if they support the required MCP transport and OAuth flow.

Using the platform requires a TakoCode account, a $10-per-month membership, and prepaid wallet credits for billable actions. The `set_preferences` tool can store autonomy, question, service-tier, and budget settings. Wallet top-ups use checkout links for amounts from $5 to $500.

## Tools and capabilities

The TakoCode MCP server provides tools for:

- Reading onboarding status, wallet details, project lists, build progress, publish status, and domain availability.
- Creating projects and starting paid coding-agent turns.
- Generating short-lived preview links and signed source ZIP downloads.
- Exporting project source to the user’s connected GitHub account.
- Publishing a project and checking its deployment.
- Searching for domains, purchasing a domain through checkout, and attaching an existing domain.

## Limitations and notes

The TakoCode MCP server is proprietary and closed-source; this repository does not contain the service implementation. Access is limited to the connected user’s TakoCode account through bearer-scoped OAuth tokens, which can be revoked from TakoCode settings.

Preview links last about four hours, and signed ZIP download links last one hour. `start_turn` and `publish_site` are paid operations. Publishing is not an autonomous charge, and wallet or domain payments require the user to finish the supplied Stripe checkout. The repository documentation and metadata are MIT-licensed, but the hosted platform and MCP implementation are not included under that repository license.

_Full upstream README: https://allmcps.com/mcp/takocode/readme_