MonoDuty
EN
Get Started

MonoDuty + Model Context Protocol

Bring monitoring into your AI coding workflow.

Use MonoDuty MCP to help set up alerting while your application’s code and operating context are still in the conversation.

Apply for 3 months of Pro See how it works

100 places · 3 months of ProManually reviewed · 90 days from activation

FROM CODE TO RESPONSEExample workflow

  1. Your coding assistant

    The service and code in context

  2. MonoDuty MCP

    Connected tools. Chosen permissions.

  3. Monitoring setup

    Review the supported configuration

  4. On-call response

    Plan and verify the notification path

Your assistant helps with setup.
You decide what it can do.

LESS CONTEXT SWITCHING

Keep alerting in the conversation.

MCP is a protocol that lets AI applications connect to external tools. With MonoDuty, supported alerting setup can be part of the conversation where you build your application.

01

Keep the context

Discuss your service, environment, and scheduled jobs in the same conversation as the code you’re changing.

02

Make the setup reviewable

Ask your assistant to explain the proposed settings, identify missing details, and check the permissions available before making changes.

03

Test the response

After setup, plan a controlled test. Check the expected incident and notification path before relying on it.

A PRACTICAL STARTING POINT

One API.
One nightly job.
One clear request.

You’ve just changed an API endpoint and the job that runs each night. Ask your assistant what should be detected while those changes are still in context.

EXAMPLE SERVICE

Public API
Should respond to availability checks.

Nightly scheduled job
Should check in after successful work.

TRY THIS IN YOUR CODING ASSISTANT
Review the API endpoint and scheduled job we changed. Identify the failures we should detect, check the tools available through our MonoDuty MCP connection, and propose the supported alerting setup. Ask for missing details before applying changes, then help us plan a controlled test.

Example request. Available actions depend on your connected tools and permissions.

  1. Connect MonoDuty MCP.

    Sign in, select your workspace, and choose the permissions you want to grant.

  2. Describe your service.

    Share the API’s expected behavior and when the nightly job should finish.

  3. Review the proposed setup.

    Confirm targets, timing, ownership, and the changes your assistant can make.

  4. Run a controlled test.

    Agree on a test and its recipients, then verify the result. Setup alone is not proof of delivery.

READY TO CONNECT

Your workspace.
Your permissions.

Add the MonoDuty endpoint to your MCP-compatible coding assistant. Sign in to MonoDuty, choose an eligible workspace, and select the access you want to allow.

Read the MCP setup guide
REMOTE MCP ENDPOINT
Loading connection details…
  • Read and reviewInspect workspace context and supported monitoring information. Proposal access is an additional choice.
  • Create with your permissionExplicit creation access lets an agent create services, Monitors, Heartbeats, and Webhooks.
  • Manage with separate consentUpdating, pausing, resuming, or deleting supported resources requires management access.

Workspace role and plan requirements apply. Connecting does not expand your plan’s limits or upgrade an existing connection’s permissions.

THREE WAYS TO KEEP WATCH

A signal for each kind of failure.

These are MonoDuty’s monitoring building blocks. What your assistant can do with them depends on the tools and permissions in your MCP connection.

When something happens

Webhooks

Connect events sent by your systems to an alerting workflow.

Explore Webhooks
When something is unreachable

Monitors

Check the availability of a website or public API endpoint.

Explore Monitors
When something doesn’t happen

Heartbeats

Watch for the expected signal from a regularly scheduled job.

Explore Heartbeats

PUT IT TO WORK

Get 3 months
of MonoDuty Pro.

We’re offering 100 places for people who want to put MonoDuty to work on a real service or scheduled job.

100participants
3months of Pro

We review applications manually. If selected, your 90 days begin when approved Pro access is activated. See the Pro plan for features and resource limits.

Applying does not create an account or subscription, activate Pro, or reserve a place. No payment card is required to apply. Read the offer details.

Start with MonoDuty MCP today
Checking application availability…

Applications are reviewed manually. Selected applicants receive 90 days of Pro from activation.

Application details

Personal and work email addresses are welcome.

For example: an API, a website, or a scheduled job. Please leave out passwords and other secrets.

We use your details to review and contact you about your application. Applying does not subscribe you to marketing emails.

By submitting, you acknowledge the offer details and Privacy policy. Terms of service apply to use of MonoDuty.

This form uses reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.

A FEW MORE DETAILS

Good questions.

More about the connection
and the Pro offer.

MCP documentation
What is MonoDuty MCP?

Model Context Protocol lets AI applications connect to external tools. MonoDuty MCP brings supported workspace, alerting, and monitoring operations into your coding conversation. The actions available depend on your account and the permissions you grant.

Can I use MonoDuty without MCP?

Yes. You can set up Webhooks, Monitors, Heartbeats, and on-call workflows in the MonoDuty dashboard. MCP is an additional way to work with supported tools.

Which coding assistants are supported?

Use an MCP-compatible coding assistant that supports remote Streamable HTTP connections and the MonoDuty OAuth sign-in flow. Client support and available actions vary; check your assistant’s connection options and the MonoDuty setup guide.

What does the three-month Pro offer include?

The offer is 90 days of MonoDuty Pro for 100 selected participants. Pro features and resource limits are listed on the pricing page. Team size helps us review your application; it does not grant extra seats or usage allowances.

When do the three months begin?

The 90-day period begins when approved Pro access is activated. Applying does not activate Pro or start the clock.

What happens when the offer ends?

This application does not create a subscription or authorize a paid renewal. If selected, you will receive activation instructions and details about continuing after the 90-day period.

How will I know whether my application was accepted?

We review applications manually and contact selected applicants at the email address provided. A receipt confirms your application was saved; it does not confirm acceptance, reserve a place, or activate Pro.