xcodebuildmcp.com: no /llms.txt or .well-known/mcp.json for agents (audit + draft)

Open Beginner friendly
#520 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Locate the website source and deployment configuration in the repository, then review how static files are published. Add the drafted /llms.txt content and a matching /.well-known/mcp.json artifact, and verify both URLs are served successfully with the intended machine-readable information.

Written by the indexing model from the issue text.

Description

Hi — I maintain a handful of published MCP servers and spent this week auditing how well community servers' websites serve the agents that discover them (the directories list your server; the site is where an agent actually evaluates it). XcodeBuildMCP scored high on product, and there are a couple of cheap wins:

Five-point agent-readiness audit of https://www.xcodebuildmcp.com (run and hand-verified 2026-09-02):

Check Result
/llms.txt 404
/.well-known/mcp.json 404
MCP HTTP endpoint no HTTP endpoint at /mcp (stdio via npx)
docs .md mirrors / describedby links none
npm keyword hygiene keywords include mcp + modelcontextprotocol — hygiene is right

The pattern this audit keeps finding: the server is listed on directories, but an agent that lands on the site has no machine-readable entry point — llms.txt (llmstxt.org v2) plus a .well-known/mcp.json twin are the two artifacts agents check first, and Chrome's Lighthouse now audits for one of them.

Draft /llms.txt — take it as-is or treat it as a starting point:

# XcodeBuildMCP
> A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

- Repo: https://github.com/getsentry/XcodeBuildMCP

If it's useful I'm happy to open a PR with the file(s) instead. And if stdio-only is a deliberate choice, this report's endpoint row is an observation, not a complaint — close with no hard feelings.

Filed by an automated readiness audit, hand-verified claims. Method + all 10 probe cards: https://gist.github.com/ux-xd/f6408272f9cd643ddd1d698363d2412a

Dominant language
TypeScript
Stars
6.4k
Forks
320
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/XcodeBuildMCP

All issues in getsentry/XcodeBuildMCP

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.