Create and read issues from Claude Code via a Tangled MCP server
October 11, 2025. Task: October 11, 2025 i saw @danabra's post about his first week of vibecoding i tried vibecoding for real. here's how it went my first week of vibecoding it's quite good if you know what you're doing underreacted.leaflet.pub and it inspired me to yak shave a bit harder than i normally might friday night yak shaving story. nate was auditing his atproto identity visualization tool (at-me.fly.dev) - it shows users their atproto identity as a hub with all the apps they use arranged around them, making the data ownership model visible. ^ this is a retro of me and claude making a tangled MCP server now registered on anthropic's registry of MCP servers it only supports a few things right now: resources tangled://status - connection status tangled://status - connection status tools all tools accept repositories in owner/repo format list_repo_branches(repo, limit) - list branches list_repo_branches(repo, limit) - list branches create_repo_issue(repo, title, body, labels) create_repo_issue(repo, title, body, labels) update_repo_issue(repo, issue_id, title, body, labels) update_repo_issue(repo, issue_id, title, body, labels) delete_repo_issue(repo, issue_id) delete_repo_issue(repo, issue_id) list_repo_issues(repo, limit) list_repo_issues(repo, limit) but i was able to do what i wanted to do when i went depth first yak shaving (note linked below i'm dictating, thus rambling a bit)! see the README if you wanna try it out! it seems like there are some architectural blockers to adding support for PRs (at least mutations). idk, still have to dig more; tools: Claude Code. Human role: The original post does not say how a person stayed involved.; limitations: The implementation currently lacks support for PR mutations due to identified architectural blockers. The source is a personal blog post, so reliability is anecdotal and lacks rigorous testing data. Human oversight is required to navigate the 'yak shaving' complexity and verify that the generated tools function correctly within the specific Tangled environment..
Tools
Published on Agent Work Atlas:
Overview
October 11, 2025
Workflow
October 11, 2025 i saw @danabra's post about his first week of vibecoding i tried vibecoding for real. here's how it went my first week of vibecoding it's quite good if you know what you're doing underreacted.leaflet.pub and it inspired me to yak shave a bit harder than i normally might friday night yak shaving story. nate was auditing his atproto identity visualization tool (at-me.fly.dev) - it shows users their atproto identity as a hub with all the apps they use arranged around them, making the data ownership model visible. ^ this is a retro of me and claude making a tangled MCP server now registered on anthropic's registry of MCP servers it only supports a few things right now: resources tangled://status - connection status tangled://status - connection status tools all tools accept repositories in owner/repo format list_repo_branches(repo, limit) - list branches list_repo_branches(repo, limit) - list branches create_repo_issue(repo, title, body, labels) create_repo_issue(repo, title, body, labels) update_repo_issue(repo, issue_id, title, body, labels) update_repo_issue(repo, issue_id, title, body, labels) delete_repo_issue(repo, issue_id) delete_repo_issue(repo, issue_id) list_repo_issues(repo, limit) list_repo_issues(repo, limit) but i was able to do what i wanted to do when i went depth first yak shaving (note linked below i'm dictating, thus rambling a bit)! see the README if you wanna try it out! it seems like there are some architectural blockers to adding support for PRs (at least mutations). idk, still have to dig more
Reported result
The author successfully created and registered the MCP server on Anthropic's registry, enabling issue management via Claude. However, the post notes that support for Pull Request mutations remains blocked by architectural constraints. No quantitative metrics on time saved or error rates were provided, only a qualitative confirmation that the author could perform desired PM tasks.
Human role
The original post does not say how a person stayed involved.
Limitations
The implementation currently lacks support for PR mutations due to identified architectural blockers. The source is a personal blog post, so reliability is anecdotal and lacks rigorous testing data. Human oversight is required to navigate the 'yak shaving' complexity and verify that the generated tools function correctly within the specific Tangled environment.
Try it
Act as a developer assistant. I want to build an MCP server for [replaceable: target platform, e.g., Tangled] to manage [replaceable: resources, e.g., issues] via [replaceable: AI tool, e.g., Claude Code]. First, analyze the API documentation for [replaceable: API URL] to identify endpoints for [replaceable: actions, e.g., create/update/delete]. Propose a tool schema with parameters like [replaceable: param names, e.g., repo, title, body]. Implement the server code in [replaceable: language, e.g., Python/TypeScript]. Before finalizing, run a dry run on a test repository [replaceable: test repo name] to verify connectivity. Show me the code and the test output for approval. Do not deploy to production or register the server until I explicitly confirm the dry run results are correct. If API limits prevent certain actions (like PRs), document these constraints clearly in the README.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.