Twowells Catenary
twowells-catenary is a Claude Code plugin for the Build phase that bridges MCP to LSP so your agent can use completions, diagnostics, go-to-definition, hover, and references from language servers.
by TwoWells · github.com/TwoWells/Catenary
Give Claude Code IDE-grade code intelligence—completions, diagnostics, go-to-definition, hover, and references—by bridging MCP clients to any Language Server Protocol server.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install twowells-catenary@TwoWells/CatenaryBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:TwoWells/Catenary") and the paste-ready config with skillselion.get_install_config("plugin:TwoWells/Catenary").
What it does
twowells-catenary is a Claude Code plugin that bridges the Model Context Protocol (MCP) and the Language Server Protocol (LSP), so your agent can request the same semantic services a desktop IDE gets from a language server. Solo and indie builders who ship with Claude Code but miss jump-to-definition, inline diagnostics, and reference search can register this plugin to expose those capabilities through MCP rather than duplicating analysis in prompts. Install it when you are in the build phase and already run one or more LSP servers for your stack; it is an integration layer, not a replacement for your editor or for writing custom MCP tools per language. The catalog lists one plugin in the bundle and keywords spanning completions, diagnostics, hover, and references—use it to tighten the feedback loop between agent edits and compiler or analyzer truth.
Highlights
- Exposes LSP capabilities (completions, diagnostics, go-to-definition, hover, references) through MCP for agent clients
- Acts as a protocol bridge so Claude Code can reuse existing language servers instead of bespoke tooling
- Targets IDE-quality intelligence for solo builders who live in agent-first workflows
- Single-plugin bundle from TwoWells/Catenary (pluginCount: 1)
- Development-category listing with 4 GitHub stars as of catalog ingest (stars not a quality score)
Why builders use it
Agent-only coding workflows often lack reliable code intelligence because MCP tools rarely speak LSP natively.
After you add the plugin, Claude Code can route structured LSP requests through MCP so edits and refactors stay grounded in real analyzer output.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 4 stars, 0 votes.
FAQ
Who is twowells-catenary for?
It is for indie developers and small teams who code primarily through Claude Code and want language-server features exposed via MCP.
When should I use twowells-catenary?
Use it during Build when you are integrating agent tooling and already have LSP servers for your languages.
How do I add twowells-catenary to my agent?
Install the TwoWells/Catenary Claude Code plugin from the repo, register it in your Claude Code plugin configuration, and point it at your LSP server endpoints.
Comments
Share how you use twowells-catenary, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.