Is there a Junction MCP server?

You don't need an MCP server to give your agent Junction. Jentic connects it directly from the API Directory: import it, store your team key once, and your agent orders lab tests or reads health data as it needs to. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

Can I limit what my agent is allowed to do with the Junction API?

Yes. For example, write a rule that allows only the summary and timeseries reads under /v2/summary/sleep/{user_id} and /v2/timeseries/{user_id}/, so a coaching agent can read one user's sleep and vitals but cannot place lab orders or delete users. Because user_id and order_id sit in the path, the same approach holds an operations agent to one order, and every call it makes is logged.

Does the Junction API have separate US and EU environments?

Yes. The Junction OpenAPI spec lists production hosts at api.us.junction.com and api.eu.junction.com, plus sandbox hosts at api.sandbox.us.junction.com and api.sandbox.eu.junction.com. Use the host that matches the region your team was created in.

What are the rate limits for the Junction API?

The Junction OpenAPI spec does not specify rate limits. Check the Junction documentation at https://docs.junction.com/ for current limits.

How do I order a lab test with the Junction API through Jentic?

Search Jentic for an intent like 'order a lab test for a patient', import Junction from the API Directory, and store your team key once. Your agent then calls POST /v3/order with the user_id, patient_details, patient_address, and the lab_test_id to run, and follows up with GET /v3/order/{order_id} to track it. To run it on your own infrastructure, install Jentic One from its GitHub repo.