Connect OpenCode to MCP servers with Arcade.dev: test a local Git server, then route tool calls through a remote OAuth-backed gateway with downstream credentials vaulted away from the model.
Connect Nous Research's Hermes Agent to a remote MCP server with Arcade.dev: native OAuth, agent-optimized tools, and downstream credentials vaulted away from the model.
Anthropic launched Claude Tag, a shared AI agent for Slack. Here's how it works and how to build a Claude Tag-style agent with Python, OpenAI, and Arcade.
EMA centralizes MCP access provisioning, but it was never designed to authorize each tool call. Here's why connected agents also need per-action authorization at runtime.
After Snowflake's intent to acquire Natoma, here's how the leading MCP runtime alternatives — Arcade.dev, AWS AgentCore, WorkOS, and Merge — compare on authorization, tool reliability, governance, and deployment flexibility.
A production-focused comparison of the top Composio alternatives in 2026 — Arcade.dev, AWS AgentCore, Merge, and Natoma — across authorization, governance, deployment, and migration complexity.
Your AI agent prototype works—until it starts acting on behalf of other people. These are the six signs your in-house agents have outgrown DIY plumbing and need an MCP runtime for identity, policy, audit, integrations, reuse, and risk ownership.
A CISO-grade rubric for AI agent governance, organized around the four concerns every CISO faces in production — and the six runtime capabilities that turn governance from spreadsheets into enforceable controls at every tool call.
Multi-user AI agents need a delegated authorization stack — OAuth 2.1, OIDC, and an MCP runtime that enforces the user/agent intersection at every tool call. This guide breaks down the nine capabilities, two identities, and one strict rule that production deployments need in 2026.
MCP runtime build vs. buy in 2026 hinges on multi-user auth, audit-grade governance, and the ongoing maintenance load of custom OAuth and policy. This guide walks engineering leaders through the decision criteria and four tipping points.
Claude Code Routines enable unattended, cloud-run workflows via scheduled, API, and GitHub event triggers — but demo-grade setups break under enterprise load. Here are five production-leaning routines for engineering teams plus the MCP runtime patterns that make them safe to ship.
A 2026 taxonomy of the MCP ecosystem — registries, gateways, and runtimes — plus a feature-by-feature comparison of 8 platforms on per-user auth, audit logs, and private infrastructure support.
Five SRE workflows — incident triage, runbook execution, postmortem drafting, SLO investigation, on-call handoffs — that Claude Code can run today, and the auth, scope, and audit gap that decides whether they make the rotation.
Securely connect AI agents to enterprise tools using an MCP runtime. Architecture guide covering OBO execution, JIT auth, token isolation, and 4 integration approaches compared.
Which enterprise software vendors are making their platforms accessible to AI agents, and which are keeping the doors locked? Arcade.dev's ToolBench rankings reveal the 5 most open and 5 most closed SaaS vendors for MCP connectivity.
Build an always-on WhatsApp AI assistant with working code. Uses Arcade.dev for secure auth, Claude Code for orchestration, and MCP for tool integration.
