mcpField
M
mayankmahavar1mg

mayankmahavar1mg

Local
github.com/tata1mgDeveloper Tools92Updated 2d ago

About mayankmahavar1mg

Developer-workflow MCP server for catalyst-core: migration guidance, debugging, and task planning.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mayankmahavar1mg": {
"command": "npx",
"args": [
"-y",
"catalyst-mcp"
],
"env": {
"GITHUB_TOKEN": "<GITHUB_TOKEN>"
}
}
}
}
Run commandnpx -y catalyst-mcp
Environment variables to set
GITHUB_TOKENSecretGitHub token used only by the create_github_issue tool. Optional — falls back to `gh auth token` if unset. Not required for any other tool.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmcatalyst-mcp1.0.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.