Tangled FAQs

Question 1

Can I monitor the connection status of Tangled?

Accepted Answer

Yes, Tangled provides a status endpoint (`tangled://status`) to monitor your connection to the Tangled PDS (Personal Data Server), including authentication and overall accessibility.

Question 2

How do I configure Tangled with my MCP client?

Accepted Answer

Tangled can be configured by providing your `TANGLED_HANDLE` and `TANGLED_PASSWORD` (an app password) via environment variables or configuration files specific to your MCP client (e.g., Claude Code, Cursor, Codex CLI). An optional `TANGLED_PDS_URL` can be specified for custom Personal Data Servers.

Question 3

What is the AT Protocol, and how does Tangled leverage it?

Accepted Answer

The AT Protocol is a decentralized social networking protocol. Tangled builds its Git collaboration platform on this protocol, allowing for a more open and interoperable ecosystem for code management and issue tracking.

Question 4

What is Tangled?

Accepted Answer

Tangled is an MCP (Multi-Client Protocol) server that integrates with Tangled.org, a Git collaboration platform built on the AT Protocol. It allows developers to manage their Git repositories and issues within their preferred MCP clients.

Question 5

What functionalities does Tangled provide for repositories?

Accepted Answer

Tangled enables users to list repository branches and issues, create, update, and delete issues, and retrieve available labels for their repositories, all accessible through connected MCP clients.

Tangled

Tangled

主要功能

使用案例

主要功能

使用案例