Datavessel

Name: Datavessel
Author: djr4

by djr4communityv0.1.0

datavessel is a hosted remote MCP server that gives AI agents read and write access to marketing and ecommerce platforms through one connection. It supports connectors like Google Analytics, Search Console, Google/Meta Ads, Shopify, WooCommerce, Shopware, Slack, and LinkedIn.

From the registry: 100+ read/write tools: GA4, Search Console, Google/Meta Ads, Shopify, WooCommerce, Shopware. BYOK.

GitHub Repository Website

Install & configure

Prerequisites

required
Create a datavessel account
Sign up for a datavessel account to use the hosted MCP server.
https://www.datavessel.io/
required
Connect your data sources in the datavessel dashboard
Authorize the marketing and ecommerce connectors you want to use (such as Google, Shopify, etc.) via OAuth in the datavessel dashboard before connecting from your MCP client.
https://app.datavessel.io
optional
Use an MCP client with remote MCP support or install/use mcp-remote
Clients with native remote MCP support can connect directly to the hosted server. Clients without native remote support need the mcp-remote bridge, typically run via npx.
```
$ npx -y mcp-remote https://mcp.datavessel.io/mcp
```

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `datavessel` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Create a datavessel account** — Sign up for a datavessel account to use the hosted MCP server. (https://www.datavessel.io/)
- **Connect your data sources in the datavessel dashboard** — Authorize the marketing and ecommerce connectors you want to use (such as Google, Shopify, etc.) via OAuth in the datavessel dashboard before connecting from your MCP client. (https://app.datavessel.io)

Optional prerequisites:
- Use an MCP client with remote MCP support or install/use mcp-remote — Clients with native remote MCP support can connect directly to the hosted server. Clients without native remote support need the mcp-remote bridge, typically run via npx. Run: `npx -y mcp-remote https://mcp.datavessel.io/mcp`

Canonical MCP server config (HTTP transport):
- url: `https://mcp.datavessel.io/mcp`

Note: This is a hosted remote MCP server using Streamable HTTP. Authentication is handled automatically via OAuth with dynamic client registration and PKCE; there is no API key or token to place in config. For clients that do not support remote MCP natively, use a stdio bridge with command 'npx' and args ['-y','mcp-remote','https://mcp.datavessel.io/mcp'].

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: This is a hosted remote MCP server using Streamable HTTP. Authentication is handled automatically via OAuth with dynamic client registration and PKCE; there is no API key or token to place in config. For clients that do not support remote MCP natively, use a stdio bridge with command 'npx' and args ['-y','mcp-remote','https://mcp.datavessel.io/mcp'].