Agents · Tools and Integrations

Your systems become tools.Inside the boundary you set.

Connect any system through MCP. Your agents call only the tools you allow, with credentials the model never sees and a person's approval where you want one.

Free to start. No credit card.
Your agentINSIDE HARDRAILS
SearchBUILT INStructured queryBUILT INRead the pageBUILT INAsk other agentsBUILT INGitHubMCPYour MCP serverMCPSend emailAPPROVAL

Built in

Every agent starts
with the tools that matter.

Search your documents, query your tables, check the source page and ask other agents. All of it runs on Retrieval-Ready Data, scored by Confidence Scoring.

SEARCH
CALL"detention after three free hours"
RESULTcontract §4.2 · p.12 · 0.97
built in · search
STRUCTURED QUERY
CALLSELECT invoice, billed, governing_rate ...
RESULT2 rows
built in · query
READ THE PAGE
CALLtariff p.12
RESULTItem 520 · first 3 hours free, then $41.00 / hr
built in · source page
ASK OTHER AGENTS
CALLinsurance-check: Carrier F
RESULTvalid to Mar 2027 · 0.96
agents as tools

Use it here, not there

Tell each tool
when it's the right one.

Every tool carries a description, what to use it for and what to avoid it for. That guidance goes into the agent's instructions, and the agent's choices are scored.

TOOL · tariff_lookup
TYPEStructured query
DESCRIBESGoverning rates by lane, item and date
USE FORAccessorial rates, detention, fuel surcharges
AVOID FORInvoice totals. Use invoice_lines instead.
APPROVALNot needed. Read only.
WHAT THE AGENT IS TOLD
tariff_lookup: governing rates by lane,
item and date.
Use for: accessorial rates, detention,
fuel surcharges.
Avoid for: invoice totals.
Tool use, this turn9 / 10

ILLUSTRATION · SAMPLE TOOL

Connect your systems

Connect it once.
Every agent you allow can use it.

Pick a server from the catalog or point to your own MCP server. Meibel detects how it signs in, reads its tools, and shares it across the projects you choose.

GitHubCATALOG
AtlassianCATALOG
NotionCATALOG
Your MCP serverANY URL

Signs in the way your server does: no sign-in, bearer token, username and password, custom headers or OAuth 2.0.

CONNECTING YOUR TMS
URLhttps://tms.example.com/mcp
SIGN-INOAuth 2.0 · detected from the URL
TOOLS FOUNDget_shipment · list_loads · get_carrier · +9
AVAILABLE TOFreight project · 3 agents

Set up once for your organization. Owners and admins manage it; everyone else attaches it to their agents.

ILLUSTRATION · SAMPLE INTEGRATION

Give your agent a system to call.

Add a built-in tool or your own MCP server, inside the boundaries you set.

Credentials the model never sees

The agent calls the tool.
Meibel holds the key.

Credentials are stored encrypted. They can be replaced, never read back. The platform attaches them to each request, so neither the agent nor its model ever sees them.

WHAT THE MODEL SEESThe tool and its result.
get_carrier(
  name="Carrier F")

→ insured: true
→ expires: 2027-03-31

No key, no token, no header. Nothing to leak into an answer or a log.

WHAT MEIBEL DOESAttaches the credential.
tms-oauth · encrypted
Authorization: Bearer ••••••••

If a sign-in lapses, the integration says it needs attention. Reconnect, and no agent changes.

YOUR SYSTEMGets an authenticated call.
POST /mcp
tool: get_carrier
200 OK
EXECUTION POLICY CHECKED FIRST

Calls route through Meibel, so Hardrails checks every one before it reaches your server.

Expose only what you choose

Every layer narrows.
Nothing widens.

A configuration sets which tools exist for a project. Hardrails narrows them per agent and session: turn one off, pin a parameter or limit its values.

YOUR SERVER
24 tools

Everything it can do.

CONFIGURATION
9 tools

What this project may use.

EXECUTION POLICY
6 tools

What this agent may call, project key pinned to OPS.

SESSION
4 tools

What this customer's session may call.

A policy can't restore a tool the configuration leaves out. The tool list is fixed for the life of each session.

ILLUSTRATION · SAMPLE INTEGRATION

A person, before it acts

Reading is automatic.
Acting can wait for a yes.

Mark any tool as needing approval and the agent pauses before it runs, with a message you write. Everything that only reads keeps moving.

1Query the rate tableDONE
2Read tariff p.12DONE
3Check the carrier's insuranceDONE
4Send the dispute emailWAITING
APPROVAL NEEDED · send_emailSend the dispute for INV-20418 to Carrier F? $82 owed, not $1,156.approval_message: "Send the dispute for {{invoice}}
to {{carrier}}? {{owed}} owed, not {{billed}}."
ApproveDecline

Every call on the record

What it called.
What came back.

Every session shows each tool call, its arguments and what came back, cited beside the documents and scored for how well it was used.

SESSION · freight-audit-agent v7 · INV-20418TOOL ACTIVITY
09:14:02tariff_lookuplane=ATL-CHI item=5201 row
09:14:03search"detention free hours"p.12 · 0.97
09:14:05tms · get_shipmentid=SH-55102arrived 08:10, left 13:40
09:14:06insurance-checkcarrier=Carrier Fvalid
09:14:09email · send_emailto=Carrier Fapproved by a person
Tool use 9 / 10Tractability 8 / 105 calls · 1 approval

Built on Meibel

Teams already ship on it.

We use Meibel to integrate generative AI into our SaaS product Specbooks+. We replaced thousands of lines of code and multiple other tools with better, measurable results.
Rob MurrayCEO, SpecBooks
Meibel is a foundational technology for our Generative AI practice. Our customers demand accountability and transparency from AI solutions, along with seamless integration into their existing operations and workflows. Meibel's platform delivers on all fronts.
Paul LiggettCEO, Cloud Eleven
Featured in

Read the case studies →

Questions

Which systems can agents use?

Any system with an MCP server, from the catalog or your own server URL. Every agent also has built-in search, structured query, the source page and other agents.

Does the model see our credentials?

No. Credentials are stored encrypted and attached by the platform to each request. They can be replaced, never read back.

Can we limit which tools an agent sees?

Yes. A configuration chooses which tools a project may use. Hardrails narrows them further for each agent and session, down to pinned parameters.

Can a tool wait for a person?

Yes. Mark it as needing approval and the agent pauses before it runs, with a message you write.

What happens when we add tools to our server?

An owner or admin refreshes the integration. New sessions pick up the change; running sessions keep the tool list they started with.

Can other apps call our agents?

Yes. Every agent is an MCP tool, so it works in Claude, Copilot, your own apps or another Meibel agent.

Start with one workload. Scale efficiently.

Refine it on one document. Run it on millions.

Start free and build an agent on one real document. Then run one real process at your real volume and measure it against what your team already knows is right.

PALETTE