Oleander

dev.oleanderPublished by oleander.devOfficial publisherv1.3.0Updated Oct 25, 2026

The all-in-one data stack for agents. Upload files, run SQL, evolve tables, and render charts.

VerifiedStreamable HTTPWeb executableDatabasesFiles & StorageData & Analytics

Overview

AI-generated overview

Oleander is a remote MCP data stack that lets an assistant upload files, run SQL, evolve tables and render charts.

What you can do
Upload files into the data stack for the assistant to work with. Run SQL queries against that data. Evolve tables as the data or schema changes. Render charts from query results. The server is described as an all-in-one data stack for agents, with no individual tools listed in the manifest.
When to use it
Useful when an assistant needs to analyze uploaded data end to end: load files, query them with SQL, adjust table structure and produce charts, without wiring up separate storage, database and visualization tools.
Requirements
A remote streamable HTTP endpoint at oleander.dev; no local package or runtime is needed. OAuth authentication is required, so the user must sign in to an Oleander account. No environment variables or headers are declared.
Before you install
OAuth sign-in grants the server access to an Oleander account, and uploaded files and query data are sent to a third-party service. Tools that upload files, run SQL or evolve tables can change stored data, so review write operations before approving them.

Installation

In SourceWeft

  1. Open Oleander in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.oleander%2Foleander/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "oleander": {
      "type": "http",
      "url": "https://oleander.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.