Author

Powerduck

2 min read

Cursor and Powerduck: Why They Are Better Together

Quick answer Short answer: The two tools sit at different layers and compose cleanly. Cursor writes the code and drives the agent; Powerduck defines the contract, generates the typed tools

Read article
2 min read

API Testing in Cursor vs a Contract-Verified Workflow

Quick answer Short answer: An editor can write a test, but it cannot prove the response conforms to the API. A contract-verified workflow checks each response against the schema and

Read article
2 min read

Why Cursor Hallucinates API Calls Without a Spec

Quick answer Short answer: An agent hallucinates an API call because it is predicting the next token, not reading your server. Without a contract, it fills in the endpoint, parameters,

Read article
2 min read

Cursor MCP Config vs an OpenAPI-Generated MCP Server

Quick answer Short answer: A hand-written MCP entry in Cursor's config is plumbing you maintain; a generated server is derived from the contract. Both expose tools to the

Read article