Use TypeStyle MCP for TypeScript style questions and formatting. Set up the local package and understand its optional Exa or Perplexity search connection.
Waldzell TypeStyle provides a local MCP tool for reviewing TypeScript style against Google's TypeScript guidance. You can submit code, ask about a rule, select a category or request formatted output through the same tool.
The configuration below starts npm package version 0.1.2 through stdio. The publisher declares Node.js 18 or later; use a currently supported release that meets that requirement. Code, query, rule and format are arguments of the typestyle tool. They are not separate callable tools.
The maintainer documents optional connections to Perplexity and Exa MCP search servers. Configure the relevant MCP URL and token in the TypeStyle process when using those services. Their account access and authentication are separate from starting this local process.
Without a configured search server, the documented fallback uses built-in rules. Do not assume a response contains a fresh external reference merely because grounding was requested; inspect the returned sources.
Ask about a specific rule or a small code sample first. Check any proposed formatting against the project's own conventions, and review the diff before applying it. Continue to use the project's compiler and lint checks to assess the resulting code.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| typestyle | Review TypeScript style, explain rules or request formatted code, with optional external reference search. |
{
"mcpServers": {
"waldzell-typestyle": {
"command": "npx",
"args": [
"-y",
"@waldzellai/server-typestyle@0.1.2"
]
}
}
}Version pinned to the package inspected for this guide. Check the publisher before upgrading.
A currently supported Node.js release meeting the package’s declared >=18 requirement, npm/npx, and a client supporting local stdio servers. Optional search connections require their own service access.
| Variable | Description | Required |
|---|---|---|
| PERPLEXITY_MCP_URL | Optional external MCP search server URL. | Optional |
| PERPLEXITY_MCP_TOKEN | Token for the corresponding optional search server. | Optional |
| EXA_MCP_URL | Optional external MCP search server URL. | Optional |
| EXA_MCP_TOKEN | Token for the corresponding optional search server. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.