Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@agent-task-compiler-mcp compile an agent contract for migrating the database schema in users.ts and orders.ts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Compile natural-language intent into a verifiable, executable agent contract — a stable JSON interface that any AI agent can consume.
LLMs are great at editing code but unreliable at specifying what they are about to do. agent-task-compiler turns vague intents into a strict AgentContract — roles, allowed tools, success criteria, constraints, and verification steps — so agents behave predictably and can be tested.
Related MCP server: yellow-pages
npm install agent-task-compilernpx agent-task-compiler "migrate database schema for users.ts and orders.ts"import { compileIntent, validateContract } from 'agent-task-compiler';
const contract = await compileIntent({
intent: 'refactor utils.ts without changing behavior',
allowedTools: ['read_file', 'write_file', 'run_tests'],
});
const { valid, errors } = validateContract(contract);
if (!valid) throw new Error(errors.join('\n'));Add to your MCP client config (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"agent-task-compiler": {
"command": "npx",
"args": ["-y", "agent-task-compiler-mcp"]
}
}
}The server exposes two tools:
compile_intent — same input as the library, returns { contract, validation }
validate_contract — validates any contract object
type AgentContract = {
version: '1.0';
intent: string;
roles: { name: string; capabilities: string[]; restrictions: string[]; model?: string }[];
tools: { name: string; args: object; required: boolean }[];
successCriteria: { id: string; description: string; check: 'automated' | 'manual' | 'llm-judge' }[];
constraints: { kind: 'scope' | 'safety' | 'resource' | 'policy'; description: string }[];
verification: { step: string; command?: string; expects?: string }[];
metadata: { compiledAt: string; parser: string; confidence: number };
};JSON Schema is at schema/contract.schema.json (also exported as agent-task-compiler/schema).
The default parser is rule-based and deterministic. Swap it for any LLM:
import { compileIntent, type IntentParser } from 'agent-task-compiler';
const llmParser: IntentParser = {
name: 'gpt-4o',
async parse(intent) {
// ...call the model, return IntentIR
},
};
await compileIntent({ intent: 'fix bug in auth.ts', parser: llmParser });Every destructive intent ships with require-confirm + dry-run restrictions.
Secrets in intent trigger a security-reviewer role and a policy constraint.
Production/migration intents require explicit approval.
strict: true fails fast on low confidence.
MIT
This server cannot be deployed
Build and run grounded business agents over MCP: agents, knowledge bases, skills, Storylines.
Immutable agent diagrams: create, edit, validate and render versioned diagrams over MCP.
MCP facade over the Nebelus Construction API. ~48 tools give full agent build parity: create/update/probe agents, edit graphs, attach knowledge and vector stores, wire connectors, set governance policies and locked guardrails, enable grounding-trace, and read deployment wiring. Purpose-built for regulated industries: data residency is enforced per region (EU / GCC-KSA), with PII controls and an audit trail. Agents are created as drafts — no deploy tool is exposed over MCP by design; publishing happens in the Nebelus console.
Free MCP tools to validate multi-agent coordination thread turns and retrieve schema/samples.
