GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Serves your design system and coding standards to coding agents, so they stop guessing.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://tseha.io/mcpRun this in your terminal
claude mcp add --transport http tseha https://tseha.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tseha": {
"url": "https://tseha.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tseha": {
"type": "http",
"url": "https://tseha.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://tseha.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.
list_projectsLists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projects the calling credential may see. Call it first in a session: the returned id is the project_id that every other tool in this server requires
list_packagesLists the component packages assigned to a project, each with its name, version, and description, and marks which one is active. Read-only. Use it to decide which npm package to import from, or to read the installed version before calling get_component_updates. It lists packages,
list_componentsLists every UI component in the project's design system, each with its name, source package, import path, and a short note on its intended use. Read-only and unpaginated: it returns the whole catalog across all packages assigned to the project, so expect a large response on big d
get_componentReturns the full specification for one component: import path, props schema, usage example, anti-patterns, when-to-use and when-not-to-use notes, Figma spec, and dependencies. Read-only. Call it before writing code that uses a component, so props and import path come from the des
search_componentsSearches the components of every package assigned to the project by use case, behavior, or description, and returns up to 10 ranked matches with a relevance score. Read-only. Use it when you can describe what the UI must do but do not know the component name. The query is free-te
get_styleReturns metadata for the project's active style: the style name, its Figma file key, when it was last synced, and a token count per available category (such as color, typography, spacing). Read-only and small - it names categories but returns no token values. Use it to inspect th
get_style_tokensReturns the project's design tokens with their names, values, and token paths. Read-only. Use it to source exact visual values for styling instead of inventing hex codes, spacing, or radii. The category argument takes exactly one of: color, typography, spacing, radius, shadow, bl
get_standardsReturns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or reviewing code, so the result follows this organization's rules rather than general defaults. Call it first without a sectio
get_component_updatesReturns per-component breaking changes and a migration guide between an installed version of the project's active component package and the latest published version. Read-only: it reports an upgrade, it never performs one. Use it when planning or reviewing a component-library upg
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified against the domain tseha.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 708 ms (HTTP 200)
No sign-in needed
Read 9 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Serves your design system and coding standards to coding agents, so they stop guessing.
Tseha is a hosted, remote MCP server. Point your coding agent at it and the agent reads your real component APIs, design tokens and coding standards instead of inventing them.
https://tseha.io/mcp (Streamable HTTP)io.tseha/tsehaThis repository holds the published server.json manifest and the connection documentation. Tseha itself is a hosted commercial service and its source is not open; there is nothing to install or build here.
Add a .mcp.json to the root of your repository:
{
"mcpServers": { "tseha": { "url": "https://tseha.io/mcp" } } }
That is the whole configuration. On first connection the agent opens an OAuth sign-in in your browser. Approve it once and the agent is connected.
| Client | Where the config lives |
|---|---|
| Claude Code | .mcp.json in the project root, or claude mcp add --transport http tseha https://tseha.io/mcp |
| Cursor | .cursor/mcp.json (per project) or ~/.cursor/mcp.json (global) |
| VS Code / GitHub Copilot, and any other MCP client | point at https://tseha.io/mcp over the HTTP transport |
This repository is also packaged as a Cursor plugin (.cursor-plugin/plugin.json plus mcp.json), so Cursor can install the connection for you instead of you editing a config file. Install it from Cursor Settings -> Plugins, or add the repository by hand from https://cursor.directory/plugins.
OAuth 2.1 with PKCE (S256). There is no API key to paste. Tseha publishes the standard discovery documents — /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource (RFC 9728) — and supports both Dynamic Client Registration and Client ID Metadata Documents, so compliant clients configure themselves.
The issued token is scoped to your organization and your role. The MCP surface is read-only for every role. Writes happen only in the Tseha admin panel.
All nine tools are read-only. Every tool except list_projects takes a project_id, which list_projects returns.
| Tool | What it returns |
|---|---|
list_projects | The projects in your organization, each with id, name and framework. Call this first — the id is required by every other tool. |
list_packages | The component packages assigned to a project, with version, and which one is active. |
list_components | Every UI component in the project's design system: name, source package, import path, intended use. |
get_component | The full spec for one component: import path, props schema, usage example, anti-patterns, when-to-use notes, Figma spec, dependencies. |
search_components | Components ranked by description, for finding one by need rather than by name. |
get_style | Style metadata for a design token collection. |
get_style_tokens | Design tokens by category: color, typography, spacing, radius, shadow, blur, or all. |
get_standards | Your organization's development standards, by section (global, react, nextjs, …). |
get_component_updates | What changed between the installed version of a component and the current one. |
iss on authorization responses, RFC 8252 §7.3 loopback redirect URIsPublished to the official MCP Registry under the DNS-verified namespace io.tseha:
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=tseha"
The manifest and documentation in this repository are published under the MIT licence.
That licence covers the contents of this repository only. It does not grant any licence to the Tseha service at https://tseha.io, which is a hosted commercial product governed by its own terms, nor any right to use the Tseha name or logo as a trademark.
Questions and issues: https://tseha.io/docs, or open an issue on this repository.