Connect Vortaex to your coding agent

1. What this does

• Your coding agent starts with your approved lessons.
• It sees lessons from past projects.
• It sees risks to watch.
• It sees what needs founder approval.
• It gets one clear next step.
• It cannot approve, reject, or rewrite approved lessons.

2. Before you start

3. Ways to connect

4. Setup steps

5. Agent config examples

Approved Vortaex accounts can connect a local MCP server to MCP-compatible coding agents. Choose the config for the agent you use. Same Vortaex server path, same agent token from Step 1; only the file format and config location change per agent.

Choose one agent. You do not need to paste every config.

{
  "mcpServers": {
    "vortaex": {
      "command": "node",
      "args": ["PATH_TO_VORTAEX_MCP_SERVER"],
      "env": {
        "VORTAEX_AGENT_TOKEN": "vtx_live_YOUR_TOKEN_HERE",
        "VORTAEX_BASE_URL": "https://vortaex.dev"
      }
    }
  }
}

6. First prompt to run

Once your coding agent shows Vortaex in its tool list, paste this:

Title: Plan the next company project

Use the Vortaex MCP server.

Call vortaex_get_agent_brief with this task:

"Help me plan the next company project."

Then answer in plain English with:
- Best next move
- Why it matters
- What to do first
- What to avoid
- What needs founder approval

7. Prompt with project ID

If your coding agent asks for a project ID, open the project in Vortaex and copy the ID from the URL.

Use the Vortaex MCP server.

Call vortaex_get_agent_brief with:

projectId: "PASTE_PROJECT_ID_HERE"
task: "Help me plan the next company project."

Read the brief first.

Then answer with exactly these five labels:

What to fix:
Why it matters:
What to do first:
What to avoid:
What needs founder approval:

8. Useful prompt examples

Each prompt expects the same five-label answer format.

• A. Plan next company project

  Copy task

  Task: "Help me plan the next company project."

• B. Prepare a client demo

  Copy task

  Task: "Prepare a client demo."

• C. Review before delivery

  Copy task

  Task: "Review this project before delivery."

• D. Explain what to avoid

  Copy task

  Task: "What should we avoid before shipping this project?"

9. Advanced prompt options

Most users should start with the simple prompt above. Use these only when you need stricter output.

10. What good output looks like

What to fix:
Make sure one company cannot see another company's approved lessons.

Why it matters:
Vortaex stores approved lessons and project rules. If the wrong company can see them, the product loses trust.

What to do first:
Check the code that reads approved lessons and confirm each lesson belongs to the right company.

What to avoid:
Do not change billing, approve lessons automatically, or touch production data without founder approval.

What needs founder approval:
Any production change, client-facing output, lesson approval, or access-rule change.

11. What Vortaex will not do

• Vortaex will not train your coding agent's model.
• Vortaex will not let your coding agent approve lessons.
• Vortaex will not let your coding agent change billing.
• Vortaex will not let your coding agent change company access rules.
• Vortaex will not let one company see another company's lessons.

Vortaex stores approved lessons outside the model. Your coding agent can read those lessons through MCP when you connect it, but approval, edits, and access rules stay inside Vortaex.

12. Troubleshooting