Productivity · Remote MCP server
Goosy
Create, organize, and publish marketing work with Goosy's tenant-scoped tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.goosybear/goosy- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- ai.goosybear
- Namespace
- Namespace verified by the MCP Registry via the domain goosybear.ai · how
- Website
- goosybear.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.goosybear.ai/api/mcp/mcp | Authorization (required, secret) |
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 Goosy
Goosy is a remote MCP server: there is nothing to install. Its endpoint is https://app.goosybear.ai/api/mcp/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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
Site checks
The website's own root, goosybear.ai, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More productivity servers
| Server | Runs |
|---|---|
| Google WorkspacePermissioned access to Gmail, Drive and Calendar via the user's own Google account. | Remote · HTTPLive check: sign-in required |
| Google WorkspaceGive AI agents access to Gmail, Calendar, Drive, and more - multi-account, manifest-driven. | Local · stdio |
| Google WorkspaceGoogle Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more. | Local · stdio |
| Google Workspace MCP Server67 curated MCP tools for Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks. | Local · stdio |
| GoreloMCP server for Gorelo's PSA ticket, client, contact, contract, asset, and time-tracking APIs. | Local · stdio |
| GorevTask management system for AI assistants with MCP protocol, templates, and bilingual support (TR/EN) | Local · stdio |
| GrabMail disposable emailDisposable email for agents: create an inbox, wait for the message, read the code. No key needed. | Remote · HTTPLive check: ✓ handshake |
| GrabzIt MCP-SERVEROfficial GrabzIt MCP server for AI web scraping, screenshots, and PDF/DOCX generation. | Local · stdio |