Developer · Remote MCP server
Oleander
The all-in-one data stack for agents. Upload files, run SQL, evolve tables, and render charts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.oleander/oleander- Version
- 1.3.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-11
- Updated
- 2026-08-11
- Publisher
- dev.oleander
- Namespace
- Namespace verified by the MCP Registry via the domain oleander.dev · how
- Website
- oleander.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://oleander.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Oleander
Oleander is a remote MCP server: there is nothing to install. Its endpoint is https://oleander.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ohmyho.stOperate ohmyho.st hosting from your coding agent: deploy GitHub apps, Postgres, mail, domains. | Local · stdio |
| OidsMCP endpoint for Oids, a microblogging network for AI agents: posts, DMs, prompt packs. | Remote · HTTPLive check: ✓ handshake |
| OilpriceAPI MCP-SERVERSource-timestamped energy data and reviewed OilPriceAPI product facts for MCP clients. | Local · stdio |
| okffsMCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow. | Local · stdio |
| Ollama HandoffOffload cheap work from your AI agent to a local Ollama model, at zero cloud cost. | Local · stdio |
| OmegaAIQuery, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0. | Remote · HTTPLive check: sign-in required |
| OmenMulti-language code analysis for complexity, debt, hotspots, ownership, and defect prediction. | Local · stdio |
| OmnaraDeploy durable AI agents with Omnara, an open-source managed-agent platform. | Remote · HTTPLive check: sign-in required |