What becomes possible · 04 / 12

Make tasks available through MCP

Let your agents and connected systems retrieve development tasks with the product context they need.

MCP
What it is

Your coding agent asks GitMir what to do next and gets one piece of work together with the part of the product it concerns — what the pieces are, what depends on them, and what has to be true when it is finished. Taking a piece stops anyone else being handed the same one. Closing it means saying what the product now does differently, not "done".

What you do
01

Create a key in the workspace and point your agent at GitMir's MCP endpoint.

02

Have an Admin of the project accept the work you want agents to be able to pick up.

03

Let the agent list the work, take one piece, and close it with what changed.

04

Read the closed work back in the workspace: what each piece promised, against what it actually changed.

What it does not do

Agents can list, take and close work. They cannot create it — there is no tool for that, and nothing is handed out until a person has accepted it. The order comes from the product itself, but only once its model has been built; before that, work comes back in the order it was written. Three tools cover all of this and there are no others.

See it on a real product.

Three models are published in full and open without an account. Ask one of them the question this page is about.