Skip to content
OOBE Protocol logo

OOBE Protocol

No-code builder that assembles AI agents on Solana, wiring them to on-chain actions and a hosted MCP server.

At a glanceswept 2026-10-12

not read yet

Use

For
creators and builders making autonomous AI agents on the Solana blockchain, including those without coding skills
Price
Price not read
Activity
Actively maintainedsite updated 4 weeks ago
Company
since 2024per their site
Runs as
No-code
What people do with it
  • build AI agents in a no-code visual editor
  • connect agents to Solana on-chain actions
  • track agent activity with on-chain analytics
The companyeach fact with its source · read 2026-10-13
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.oobeprotocol.sap.mcp/sap-mcpverified in the MCP registry
  • Stateanswers, 453 toolschecked 2026-10-13
  • Address to connectmcp.sap.oobeprotocol.ai/mcp

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Developer tools tools →

Questions this page answers
  • What is OOBE Protocol?

    No-code builder that assembles AI agents on Solana, wiring them to on-chain actions and a hosted MCP server. It is listed in the Atlas under Developer tools.

  • Who is OOBE Protocol for?

    creators and builders making autonomous AI agents on the Solana blockchain, including those without coding skills

  • Do people use OOBE Protocol?

    Little sign of use.

  • Is OOBE Protocol still maintained?

    Actively maintained: site updated 4 weeks ago.

  • What are alternatives to OOBE Protocol?

    In Developer tools, by use: GoodBarber, Assembly Studio, Bolt, Adalo, CROO, Caspi.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.