Byteland
Server Details
A night city of developers: README cards, repo contributor streets, a year in lights, project rooms.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 16 tools
Most tools have clearly distinct targets (building vs street vs profile vs project vs room vs thread), and the single-vs-list splits (get_project/list_projects, read_room/read_thread) are clear. However, the cluster of 'street/building' tools (get_street, repo_street, preview_building, get_building) and the metric-style tools (get_stats, popular) overlap enough that an agent could occasionally hesitate.
The core CRUD-style operations follow verb_noun (get_building, list_rooms, read_room, preview_building), but several tools are bare nouns or adjectives (about, live, popular, search, repo_street, year_in_lights), mixing conventions. Still readable, but not a predictable pattern.
16 tools is at the upper edge of ideal, but the domain (city overview, buildings, streets, profiles, projects, rooms, threads, stats, GitHub integrations) justifies the breadth. No obvious throwaway tools, though a couple could potentially merge (e.g. get_building/get_street).
Read coverage is broad (buildings, streets, profiles, projects, rooms, threads, leaderboards, search, GitHub data), but the surface is entirely read-only: rooms have messages/threads/reactions yet there is no tool to post, create threads, or react. Also, get_project dead-ends on private projects, which list_projects only flags as hidden.
Available Tools
16 toolsaboutWhat Byteland isAInspect
Short description of Byteland: what buildings, rooms and lights stand for, units, privacy rules and supported languages. A good first call.
Inputs: no named parameters.
get_buildingBuilding detailBInspect
Public detail of one building: the owner’s profile, rooms and their states, machine-readable parts and the building recipe.
Inputs: ref (required), lang, mode, seed.
get_profileProfileBInspect
A developer’s or company’s profile: bio, links (GitHub, website, socials), badges, projects and open-source contributions. If not on the street, looks for a saved profile, then GitHub; otherwise generates a sample (preview:true).
Inputs: handle (required), lang, mode, seed, +1 more.
get_projectOne projectCInspect
A single project of a profile. Returns nothing for private projects.
Inputs: handle (required), project (required), lang, mode, +2 more.
get_statsVisits of a buildingCInspect
Unique visits (all time and this week), project views, weekly rank and the last 14 days for one username.
Inputs: handle (required).
get_streetA stretch of the streetBInspect
Buildings in a range (owner, type, floors, light counts) and gaps (alleys, empty lots). Positions in centimetres, at most 80000 cm.
Inputs: to, from, lang, mode, +1 more.
list_projectsProjectsBInspect
A profile’s projects: state, description, stack, links (repo, site) plus open-source contributions. Private projects appear only as hidden:true.
Inputs: handle (required), lang, mode, seed, +1 more.
list_roomsRooms of a personAInspect
The project rooms of a person that have been used (every public project of a resident has a room, open by default; one nobody wrote in is empty and not listed): mode (open or read-only), channels with message counts, forum threads, last activity and how many are in voice. Closed rooms and private projects never appear.
Inputs: handle (required).
liveWhat is happening nowAInspect
Voice rooms with people in them right now and the rooms with messages in the last 48 hours. Voice presence comes from the running site (BYTELAND_URL, default http://127.0.0.1:8787); without it only the recent rooms are known.
Inputs: no named parameters.
popularMost visitedAInspect
The leaderboard: buildings by unique visits this week (or period: "all"), the most viewed projects and the newest residents. A visit counts once per person per day; owners do not count themselves.
Inputs: period.
preview_buildingDeed previewBInspect
Builds a user's building as if it stood at the start of a street (GitHub repositories become rooms). The preview is not added to the city. Append the returned url_hash to index.html to open it on the site.
Inputs: handle (required), lang, github.
read_roomRead a roomBInspect
The latest messages of one channel of a project room (default: its first channel) and the forum threads (idea, review, question, announcement) with reply and reaction counts.
Inputs: handle (required), project (required), limit, channel.
read_threadRead a forum threadCInspect
One forum thread of a project room with all of its replies and reactions.
Inputs: handle (required), thread (required), project (required).
repo_streetA repository as a streetAInspect
Any public GitHub repository as a Byteland street: its top contributors (bots left out) with commit counts, who pushed in the last 30 days (their lights are on), who lives in Byteland, the total number of contributors, and the image and page links (street: an SVG for READMEs, page: the street page). total is null when GitHub will not list the contributors of a very large history; then the people are this month's committers.
Inputs: owner (required), repo.
searchSearch BytelandBInspect
Find people, projects and stacks across every resident of the city (people, projects, stacks), plus buildings on the street by username, name, project or technology (results). Private projects never appear.
Inputs: query (required), lang, mode, seed, +1 more.
year_in_lightsA developer’s yearAInspect
Anyone's GitHub contribution calendar for one year, by month: contributions per day (with GitHub's quartile level), the total, days with contributions, the longest and the current streak and the busiest month. image is the Byteland picture of it (twelve month buildings, one window per day).
Inputs: handle (required), year.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
The open-source talent graph for humans and AI agents. Find developers.
GitHub stats, Wrapped, comparisons and README cards for any user, repository or organization.
Find software engineers by what they built on GitHub: search, similar, enrich, deep research.
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceCreate GitHub profile and repository cards for READMEs, link previews and social posts.105 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create GitHub profile and repository cards from live GitHub data, returning SVG/PNG links and Markdown/HTML embed snippets. Also supports template and palette discovery, card management, and optional local README updates.15MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to generate customizable static SVG cards from public GitHub contribution calendars and profile metrics, including isometric skylines, stats, language distribution, repository constellations, activity timelines, and combined views, with local rendering through MCP.MIT
- AlicenseNot gradedqualityDmaintenanceAnalyzes GitHub and local repositories to automatically generate visual architectural diagrams such as dependency graphs, class diagrams, and data flow diagrams.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.