I wrote about why llms.txt is more valuable than MCP servers for developers building side projects.
The key difference:
- MCP servers let AI agents execute tasks for you
- llms.txt lets AI agents write code for you
When building a side project, you don't need AI to create one deep link. You need code that integrates deep link logic throughout your app.
Think of it as:
- MCP = catches fish for you
- llms.txt = teaches you how to fish
We've implemented both at Limelink, but llms.txt has been far more impactful for developer adoption. When someone types "@https://limelink.org/llms.txt" in Cursor and asks for integration code, they get working code in seconds.
Curious what other SaaS builders think about this distinction.
vgb3766•1d ago
The key difference: - MCP servers let AI agents execute tasks for you - llms.txt lets AI agents write code for you
When building a side project, you don't need AI to create one deep link. You need code that integrates deep link logic throughout your app.
Think of it as: - MCP = catches fish for you - llms.txt = teaches you how to fish
We've implemented both at Limelink, but llms.txt has been far more impactful for developer adoption. When someone types "@https://limelink.org/llms.txt" in Cursor and asks for integration code, they get working code in seconds.
Curious what other SaaS builders think about this distinction.