AndyL
With this week’s release, ElixirLS bundles an experimental MCP Server. (see CHANGELOG)
Highlights
- Added Call hierarchy provider implementing LSP textDocument/prepareCallHierarchy, callHierarchy/incomingCalls and callHierarchy/outgoingCalls
- ElixirLS now bundles a number of experimental LLM oriented tools exposed as custom commands and a builtin MCP server. The tools focus on model friendly text interface instead of typical IDE oriented LSP API methods. Refer to README.md on how to connect to the MCP server. The tools include:
find_definition- Find and retrieve the source code of symbols.get_environment- Retrieve environment at location with aliases, imports, requires and more.get_docs- Aggregate and return comprehensive documentationget_type_info- Extract typespecs and contracts.find_implementations- Find all implementations of behaviours and protocols.get_module_dependencies- Analyze module dependency relationships- Unofficial support for elixir 1.19
Thanks to @lukaszsamson for this new feature. I’m curious to hear user reports!
- configuring to use with Claude Code, OpenCode, etc.
- compare/contrast with Tidewave
- integration with UsageRules or other coding aids
- pro-tips, benefits, drawbacks, opportunities, concerns, etc.
Where Next?
Trending in Dev Env & Tools
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
Interesting. Looks like it’s enabled by default so for those of us who want to turn it off
elixirLS.mcpEnabled = falsewill take care of it.I’m curious how many here are now using these agentic tools. Do we have a rough percentage?
arcanemachine
Shouldn’t this be an opt-in feature?
Personally, I just started playing with MCP very recently. I’m working with Ollama and Open Web UI. I tried getting Tidewave to work… I got to respond to my requests, but I couldn’t actually get anything useful out of it. It wouldn’t even eval my “hello world” function.
sodapopcan
Could always start a poll!
arcanemachine
The newest patch release makes MCP opt-in, not opt-out:
Tyson
I recently went down this road, too. My gut said agents could benefit from language server tools just like us humans. Every time I asked the LLM whether “semantic tools” offered a benefit over their built-in “text tools”, the agent (okay, it was Claude) responded enthusiastically that, “yes, they are much more powerful than simple text-based tools!”
But in actual usage I rarely saw Claude using them effectively. Often it would try the LS tools, fail to get a good result, then fall back to its built-ins.
So I finally asked Claude to perform some refactor tasks with and without the LS tools, and to give an honest report on the comparative advantages, and it told me the semantic tools were a cool idea but were “optimized for human cognitive limitations and offer no benefit in an agentic AI context.”
I have since abandoned this approach and have seen no dip in the quality of Claude’s output. I would love to be convinced that the problem was my implementation, not the underlying concept. But so far my conclusion is this is not a productive direction for leveraging the strengths of AI in a dev environment.
[edit: Clarification that I was trying to use my own MCP tools during this exploration, not the ElixirLS MCP tools.]
cvkmohan
Thanks. My experience is something similar. When I am using claude cli - firstly, it does not use the tools all that much - and - repeated nudging does not help much. In fact, if we are using plain claude cli - there will be zero difference between having any MCP or completely raw setup.
However, I have realized things change dramatically once we change the agent. Two examples that I can readily show:
Again both these tools (Zed, OpenCode) are using LSP or some semantic tool as part of the prompt. And it is showing its impact. How can it be enhanced is the question. That is where everyone is still in exploratory mode.
I can say with reasonable conviction that these graph databases, vector embeddings etc. are not that useful - atleast for code generation.
Tyson
Yes! We all, including the folks developing coding agents, are figuring this out at the same time!
Interesting about your improved results with Zed/OpenCode–they must have more clever system prompts? I will try some side-by-side comparisons vs. Claude Code…
[edit: Sorry for somewhat hijacking this ElixirLS thread; I will try your MCP tools too!]