Skip to content
actionlake
Start free

Connectors · Industry

Stedi Healthcare MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Stedi Healthcare and the rest of your systems. It gives your agent 79 Stedi Healthcare actions (49 reads, 25 writes and 5 that wait for a confirmation) and holds the Stedi Healthcare credential itself, so the agent never does. It paces Stedi Healthcare's limits and records every call.

Connect Stedi Healthcare freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "stedi_healthcare.destination_events.list",  intent: "check which Stedi Healthcare account is connected"}# List Event Destination Events · read · 1 upstream call
  • 79actionsin one signed file
  • 49readlook, never change
  • 25writecreate and update
  • 5wait for a yesdestructive, confirmed first

Set up

Connect Stedi Healthcare in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Stedi Healthcare.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyStedi API key (portal.stedi.com > Settings > API keys)
    account { op: "connections.requirements", service: "stedi_healthcare" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "stedi_healthcare.destination_events.list" }# list event destination events · read · 1 upstream callcheck { action: "stedi_healthcare.event_destinations.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Stedi Healthcare at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
300 calls a minute, per connection
API covered
Stedi Healthcare clearinghouse (eligibility 270/271, claims 837P/I/D, claim status 276/277, ERAs 835, enrollment, payers, event destinations) API Stedi Healthcare 2024-04-01, Claims 2025-03-07, Core 2023-08-01, Enrollment 2024-09-01, Event Destinations 2026-02-01, Manager 2024-04-01, Payers 2024-04-01healthcare.us.stedi.com/2024-04-01
Built from
Stedi Healthcare's documentation, read 23 October 2026stedi.comGitHub
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
7 of 49 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Stedi Healthcare up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Stedi Healthcare.

79 actions in 27 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 49readlook, never change
  • 25writecreate and update
  • 5destructivewait for a confirmation

  1. Executions

    9

    8 read · 1 write · 0 destructive

    List Executions · List Execution Faults · List Execution Transactions · List Polling Executions

  2. Transactions

    8

    8 read · 0 write · 0 destructive

    List Transactions · List Polling Transactions · Get Transaction · Get Transaction Attachment Document Url

  3. Event destinations

    7

    3 read · 2 write · 2 destructive

    Create Event Destination · List Event Destinations · Update Event Destination · Get Event Destination

  4. Enrollments

    6

    3 read · 2 write · 1 destructive

    Create Enrollment · Export Enrollments Csv · List Enrollments · Get Enrollment

  5. Providers

    5

    2 read · 2 write · 1 destructive

    List Providers · Create Provider · Get Provider · Update Provider

  6. Batch eligibility

    4

    3 read · 1 write · 0 destructive

    Get Batch Items · Batch Eligibility Polling · Batch Eligibility Checks · Get Batch

  7. Claims

    3

    3 read · 0 write · 0 destructive

    List Claims · Get Claim Timeline · Get Claim

  8. Eligibility checks

    3

    3 read · 0 write · 0 destructive

    Eligibility Check · Eligibility Raw X12Check · Create Eligibility Check

19 more areas · 34 actions
  • Enrollment documents 3
  • Payers 3
  • Professional claim submissions 3
  • Claim attachments 2
  • Claim status 2
  • Dental claims 2
  • Destination events 2
  • Institutional claims 2
  • Insurance discovery 2
  • Outbound transactions 2
  • Professional claims 2
  • Transaction groups 2
  • Claim acknowledgments 1
  • Claim PDFS 1
  • Coordination of benefits 1
  • Enrollment tasks 1
  • Events 1
  • Fragments 1
  • Remittances 1

Top actions

The Stedi Healthcare API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 7 of Stedi Healthcare's 7 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
stedi_healthcare.destination_events.listList Event Destination EventsLists all events for your account. Results are paginated.readautomation.webhook_delivery.list33 connectors
stedi_healthcare.event_destinations.createCreate Event DestinationCreates an event destination. Returns destination details and a signing secret for verifying event payloads.writeautomation.webhook.create209 connectors
stedi_healthcare.event_destinations.listList Event DestinationsLists all destinations configured for your account. Results are paginated.readautomation.webhook.list202 connectors
stedi_healthcare.event_destinations.updateUpdate Event DestinationUpdates an existing destination configuration.writeautomation.webhook.update175 connectors
stedi_healthcare.event_destinations.deleteDelete Event DestinationDeletes an existing destination. This action is irreversible. Deleting a destination that is already deleted succeeds with the same response (idempotent).destructiveautomation.webhook.delete211 connectors
stedi_healthcare.destination_events.getGet Event Destination EventRetrieves the details of an existing event by its identifier.readautomation.webhook_delivery.get20 connectors
stedi_healthcare.providers.listList ProvidersLists providers with optional filtering and pagination.readthis connector
stedi_healthcare.claims.listList ClaimsRetrieve a paginated list of claim records, newest first. Filter by status, patient control numbers, or submission time.readthis connector
stedi_healthcare.payers.listList Payer RecordsList Stedi's supported payers in JSON format.readthis connector
stedi_healthcare.events.retryRetry EventThis endpoint retriggers the specified processing event.writethis connector
stedi_healthcare.payers.searchSearch PayersSearch for payers by name, ID, or alias.readthis connector
stedi_healthcare.claims.timelineGet Claim TimelineRetrieve a paginated list of a claim's timeline entries, newest first. Timeline entries include submissions, acknowledgments, and claim payment information.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Stedi Healthcare actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List the companies in Stedi Healthcare and flag likely duplicates by name or domain.

    callsstedi_healthcare.providers.list

  2. Writewrite

    Create Event Destination in Stedi Healthcare. Show me exactly what you will send before you save it.

    callsstedi_healthcare.event_destinations.create

  3. Across systemsread

    Which Stedi Healthcare companies have invoices in ConnectWise PSA, and how many each?

    callsstedi_healthcare.providers.listconnectwise_manage.invoices.list

Across your systems

Stedi Healthcare, joined to the rest of your business.

One ask fetches from Stedi Healthcare and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which Stedi Healthcare companies have invoices in ConnectWise PSA, and how many each?

    stedi_healthcare.providers.list + connectwise_manage.invoices.list, on crm.company · ConnectWise PSA

  • Which Stedi Healthcare companies have invoices in NetSuite, and how many each?

    stedi_healthcare.providers.list + netsuite.views.invoices, on crm.company · NetSuite

Also mapped by other connectorscrm.company 227
ask
ask {  intent: "which Stedi Healthcare companies have invoices in ConnectWise PSA, and how many each",  steps: [    { action: "stedi_healthcare.providers.list", as: "co", input: {}, limit: 100, max_pages: 5 },    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "co",        right: "inv",        on: "crm.company",        group_by: "co.name",        select: ["co.name", "count(inv.id) as invoices"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Stedi Healthcare

Destructive actions wait for a yes.

5 Stedi Healthcare actions are destructive. These are all of them:

  • Delete Event Destinationstedi_healthcare.event_destinations.delete
  • Delete Providerstedi_healthcare.providers.delete
  • Delete Enrollmentstedi_healthcare.enrollments.delete
  • Delete Enrollment Documentstedi_healthcare.enrollment_documents.delete
  • Rotate Event Destination Secretstedi_healthcare.event_destinations.rotate_secret

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dostedi_healthcare.event_destinations.deleteconfirm_policy: human

Delete Event Destination?

intent: the user asked me to delete Event Destination

run suspended · waiting for a named person · key stedi-healthcare-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "stedi-healthcare-agent",  allowed_actions: ["stedi_healthcare.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "stedi_healthcare.event_destinations.delete", approver: "[email protected]" },    { match: "stedi_healthcare.providers.delete", approver: "[email protected]" },    { match: "stedi_healthcare.enrollments.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Stedi Healthcare only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Stedi Healthcare costs on actionlake.

Every Stedi Healthcare action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Stedi Healthcare refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 79 Stedi Healthcare actions
  • 79actions pageeach page of a long list is one call
  • 7reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Stedi Healthcare action.

79 actions by area: the id your agent calls, what it does, and its effect.

Executions9
  • stedi_healthcare.executions.getGet Executionread
  • stedi_healthcare.executions.get_input_urlGet Execution Input Document Urlread
  • stedi_healthcare.executions.get_metadata_urlGet Execution Metadata Document Urlread
  • stedi_healthcare.executions.get_output_urlGet Execution Output Document Urlread
  • stedi_healthcare.executions.listList Executionsread
  • stedi_healthcare.executions.list_faultsList Execution Faultsread
  • stedi_healthcare.executions.list_transactionsList Execution Transactionsread
  • stedi_healthcare.executions.pollList Polling Executionsread
  • stedi_healthcare.executions.retryRetry Executionswrite
Transactions8
  • stedi_healthcare.transactions.getGet Transactionread
  • stedi_healthcare.transactions.get_attachment_urlGet Transaction Attachment Document Urlread
  • stedi_healthcare.transactions.get_fragmentGet Transaction Fragmentread
  • stedi_healthcare.transactions.get_fragment_output_urlGet Transaction Fragment Output Document Urlread
  • stedi_healthcare.transactions.get_input_urlGet Transaction Input Document Urlread
  • stedi_healthcare.transactions.get_output_urlGet Transaction Output Document Urlread
  • stedi_healthcare.transactions.listList Transactionsread
  • stedi_healthcare.transactions.pollList Polling Transactionsread
Event destinations7
  • stedi_healthcare.event_destinations.createCreate Event Destinationwrite
  • stedi_healthcare.event_destinations.deleteDelete Event Destinationdestructive
  • stedi_healthcare.event_destinations.getGet Event Destinationread
  • stedi_healthcare.event_destinations.get_secretGet Event Destination Secretread
  • stedi_healthcare.event_destinations.listList Event Destinationsread
  • stedi_healthcare.event_destinations.rotate_secretRotate Event Destination Secretdestructive
  • stedi_healthcare.event_destinations.updateUpdate Event Destinationwrite
Enrollments6
  • stedi_healthcare.enrollments.createCreate Enrollmentwrite
  • stedi_healthcare.enrollments.deleteDelete Enrollmentdestructive
  • stedi_healthcare.enrollments.export_csvExport Enrollments Csvread
  • stedi_healthcare.enrollments.getGet Enrollmentread
  • stedi_healthcare.enrollments.listList Enrollmentsread
  • stedi_healthcare.enrollments.updateUpdate Enrollmentwrite
Providers5
  • stedi_healthcare.providers.createCreate Providerwrite
  • stedi_healthcare.providers.deleteDelete Providerdestructive
  • stedi_healthcare.providers.getGet Providerread
  • stedi_healthcare.providers.listList Providersread
  • stedi_healthcare.providers.updateUpdate Providerwrite
Batch eligibility4
  • stedi_healthcare.batch_eligibility.getGet Batchread
  • stedi_healthcare.batch_eligibility.list_itemsGet Batch Itemsread
  • stedi_healthcare.batch_eligibility.pollBatch Eligibility Pollingread
  • stedi_healthcare.batch_eligibility.submitBatch Eligibility Checkswrite
Claims3
  • stedi_healthcare.claims.getGet Claimread
  • stedi_healthcare.claims.listList Claimsread
  • stedi_healthcare.claims.timelineGet Claim Timelineread
Eligibility checks3
  • stedi_healthcare.eligibility_checks.checkEligibility Checkread
  • stedi_healthcare.eligibility_checks.check_raw_x12Eligibility Raw X12Checkread
  • stedi_healthcare.eligibility_checks.check_simplifiedCreate Eligibility Checkread
Enrollment documents3
  • stedi_healthcare.enrollment_documents.create_uploadCreate Enrollment Document Uploadwrite
  • stedi_healthcare.enrollment_documents.deleteDelete Enrollment Documentdestructive
  • stedi_healthcare.enrollment_documents.get_download_urlCreate Enrollment Document Downloadread
Payers3
  • stedi_healthcare.payers.getGet Payer Recordread
  • stedi_healthcare.payers.listList Payer Recordsread
  • stedi_healthcare.payers.searchSearch Payersread
Professional claim submissions3
  • stedi_healthcare.professional_claim_submissions.createCreate Professional Claim Submissionwrite
  • stedi_healthcare.professional_claim_submissions.getGet Professional Claim Submissionread
  • stedi_healthcare.professional_claim_submissions.validateValidate Professional Claim Submissionread
Claim attachments2
  • stedi_healthcare.claim_attachments.create_uploadCreate Claim Attachment Filewrite
  • stedi_healthcare.claim_attachments.submit_raw_x12Submit Claim Attachment Raw X12write
Claim status2
  • stedi_healthcare.claim_status.checkClaim Statusread
  • stedi_healthcare.claim_status.check_raw_x12Claim Status Raw X12read
Dental claims2
  • stedi_healthcare.dental_claims.submitDental Claims Submissionwrite
  • stedi_healthcare.dental_claims.submit_raw_x12Dental Claims Raw X12Submissionwrite
Destination events2
  • stedi_healthcare.destination_events.getGet Event Destination Eventread
  • stedi_healthcare.destination_events.listList Event Destination Eventsread
Institutional claims2
  • stedi_healthcare.institutional_claims.submitInstitutional Claims Submissionwrite
  • stedi_healthcare.institutional_claims.submit_raw_x12Institutional Claims Raw X12Submissionwrite
Insurance discovery2
  • stedi_healthcare.insurance_discovery.checkInsurance Discovery Checkread
  • stedi_healthcare.insurance_discovery.getGet Insurance Discovery Checkread
Outbound transactions2
  • stedi_healthcare.outbound_transactions.createCreate Partnership Outbound Transactionwrite
  • stedi_healthcare.outbound_transactions.generate_ediGenerate Ediwrite
Professional claims2
  • stedi_healthcare.professional_claims.submitClaims Submissionwrite
  • stedi_healthcare.professional_claims.submit_raw_x12Claims Raw X12Submissionwrite
Transaction groups2
  • stedi_healthcare.transaction_groups.add_transactionCreate Transaction Groupwrite
  • stedi_healthcare.transaction_groups.generate_ediGenerate Transaction Group Ediwrite
Claim acknowledgments1
  • stedi_healthcare.claim_acknowledgments.get_277Convert Report277read
Claim PDFS1
  • stedi_healthcare.claim_pdfs.export_by_business_idExport PDFread
Coordination of benefits1
  • stedi_healthcare.coordination_of_benefits.checkCoordination Of Benefitsread
Enrollment tasks1
  • stedi_healthcare.enrollment_tasks.updateUpdate Task Postwrite
Events1
  • stedi_healthcare.events.retryRetry Eventwrite
Fragments1
  • stedi_healthcare.fragments.createCreate Outbound Fragmentwrite
Remittances1
  • stedi_healthcare.remittances.get_835Convert Report835read

Questions

The Stedi Healthcare MCP server, answered.

Is there a Stedi Healthcare MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 79 Stedi Healthcare actions across executions, transactions, event destinations and enrollments, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Stedi Healthcare.

What do I need to connect Stedi Healthcare?

Stedi API key (portal.stedi.com > Settings > API keys). The free call account { op: "connections.requirements", service: "stedi_healthcare" } lists exactly what to paste.

Can an AI agent delete or change things in Stedi Healthcare?

Only if its key allows it, and only with an explicit confirmation. 5 Stedi Healthcare actions are destructive, including delete Event Destination, delete Provider and delete Enrollment. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Stedi Healthcare API limit?

actionlake paces every call to the limits in the Stedi Healthcare service file: 300 calls a minute per connection. Repeated reads are answered from cache (7 Stedi Healthcare actions can be), which never reaches Stedi Healthcare.

What does a Stedi Healthcare action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (79 Stedi Healthcare actions page). Cache hits, searches, dry runs and calls Stedi Healthcare refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Stedi Healthcare API does it cover?

The Stedi Healthcare clearinghouse (eligibility 270/271, claims 837P/I/D, claim status 276/277, ERAs 835, enrollment, payers, event destinations) API Stedi Healthcare 2024-04-01, Claims 2025-03-07, Core 2023-08-01, Enrollment 2024-09-01, Event Destinations 2026-02-01, Manager 2024-04-01, Payers 2024-04-01 at healthcare.us.stedi.com/2024-04-01. It is built from Stedi Healthcare's documentation as read on 23 October 2026. 79 actions in 27 areas, each one in the signed service file (version 1.0.0).

Can I combine Stedi Healthcare with my other systems?

Yes. ask joins Stedi Healthcare to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Stedi Healthcare maps crm.company, which 227 other connectors also map.

Does actionlake keep my Stedi Healthcare data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Stedi Healthcare credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Stedi Healthcare

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Stedi Healthcare; the name is the vendor's own. Counts are from the Stedi Healthcare service file, version 1.0.0.

Give your agent Stedi Healthcare today.

Connect Stedi Healthcare freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.