Tools
Actions the model can call, like audit_repository or list_findings.
MCP CONNECTORS & PLUGINS COMING SOON
Soon you’ll ask Claude, Cursor or VS Code to audit a repository, explain a finding or draft a fix, with Aster’s checks behind the answer. It isn’t available yet. Here is how it will work.
Illustration: in an AI coding tool, you ask it to audit demo/storefront. The tool calls Aster’s planned audit_repository tool, Aster reads the repository read-only and returns three findings, and the assistant summarises the high-severity one and offers to draft a fix that asks before anything is written.
WHAT IS MCP
The Model Context Protocol is an open standard. An AI app (the host) runs a small client for each server it connects to. A server, like Aster’s, describes what it can do, and the model calls it when your question needs it.
Connect. You add Aster once. Your AI app starts an MCP client for it and you sign in with OAuth, so there are no keys to paste.
Discover. The client asks what Aster offers (tools/list) and learns each tool’s name, purpose and inputs.
Call. When your question needs it, the model calls a tool (tools/call audit_repository). Aster reads the repository, read-only.
Answer. Aster returns findings with file, line and evidence. Your AI app shows them and answers in plain language.
Actions the model can call, like audit_repository or list_findings.
Context it can read, like your latest saved report.
Ready-made starters, like “Review my last audit”.
LOCAL · STDIO runs on your machine REMOTE · HTTP + OAUTH hosted, sign in once. Aster plans a hosted server.
PLANNED TOOLS · ILLUSTRATION
Pick a question to see the tool call behind it. Reading tools run without changing anything; anything that could change code asks you first.
audit_repositoryREAD-ONLY{ "repo": "demo/storefront" }RETURNS
list_findingsREAD-ONLY{ "repo": "demo/storefront", "severity": "high" }RETURNS
app/api/search.ts · line 9explain_findingREAD-ONLY{ "finding": "sql-raw-query", "level": "beginner" }RETURNS
draft_fixASKS FIRST · PAID PLANS{ "findings": ["sql-raw-query"], "model": "from Aster’s library" }RETURNS
open_draft_prYOUR APPROVAL · ASTER FIXES{ "patch": "fix-search-query", "draft": true }RETURNS
Planned tools, shown as an illustration. Names, inputs and plan availability may change before launch.
WHERE IT WILL WORK · PLANNED
Most AI coding tools can add an MCP server in a minute. Here is where we plan to support Aster, and how you’d add it.
Settings → Connectors → add a custom connector
PLANNEDclaude mcp add, or the Aster plugin
Settings → MCP, or .cursor/mcp.json
.vscode/mcp.json in your workspace
Cascade → MCP servers
PLANNEDConnectors → add a remote server
PLANNEDAdd a server to its MCP config
PLANNEDRemote server URL + OAuth sign-in
PLANNEDProduct names and logos belong to their owners and show where we plan to support Aster. No partnership is implied, and none of these connections is available yet.
CLAUDE CODE PLUGIN · PLANNED
A Claude Code plugin is a folder that bundles skills, slash commands, subagents, hooks and MCP servers. You install it from a marketplace with /plugin, and everything arrives together.
Select a file to see what it would add.
Version and description, so your marketplace shows what you’re installing.
/aster:auditRun an audit of the current repository from the chat and get the findings back.
/aster:fixDraft a fix for selected findings. Shows the model and cost, and asks before anything is written.
Claude can hand a diff to this agent, which checks it against Aster’s findings.
Suggests a fresh audit after a big change. Off unless you turn it on.
The same hosted server as the connector, signed in with OAuth.
Plugins run with your permissions. Install only from sources you trust.
SAFE BY DESIGN
The same rules as the dashboard, wherever you use Aster.
Illustration: reading tools run straight away; the draft_fix tool stops and asks you to allow it, showing the model and credit cost.
SETUP PREVIEW
A sneak peek at the setup in each tool. It won’t connect yet: the address below is an example.
claude mcp add --transport http aster <ASTER_MCP_URL — published at launch>
Then run /mcp in Claude Code and sign in with Aster.
{
"mcpServers": {
"aster": { "url": "<ASTER_MCP_URL — published at launch>" }
}
}Cursor asks you to sign in when it connects.
{
"servers": {
"aster": { "type": "http", "url": "<ASTER_MCP_URL — published at launch>" }
}
}Use it from GitHub Copilot in agent mode. Note the top-level key is servers.
Works on claude.ai and Claude desktop. Team and Enterprise owners add connectors in organization settings.
QUESTIONS
Not yet. The MCP server and the Claude Code plugin are planned and not available. Today you run audits and fixes in the Aster dashboard, and you can paste a finding into any assistant.
An open standard that lets AI apps such as Claude, Cursor and VS Code connect to outside tools through one common interface, so a tool built once works in many apps.
Not on its own. Reading tools only read. Drafting a fix shows the model and cost and asks you first, and publishing a draft pull request still needs the separate Aster Fixes authorization. Nothing is merged automatically.
We plan to start with tools that support remote MCP servers with OAuth, such as Claude, Claude Code, Cursor and VS Code. We don’t publish dates; get notified and we’ll email you when it’s ready.
We’ll share plan details at launch. Today, audits start free and AI-assisted fixes are part of paid plans; we expect the same split.
Add servers only from sources you trust, check what each tool can do, and keep your AI app’s approval prompts on. Aster’s server will be read-only by default and use OAuth, so you can revoke it any time.
Email us and we’ll write when Aster’s MCP server and plugin are ready. Until then, your first audit is free in the dashboard.