Content Tools

flowercomputer.com

Provides access to Flower's company overview, published posts, post search, and public contact information.

1 endpoint6 known toolsFirst detected September 15, 2026Last detected September 15, 2026

ENDPOINT 1

https://mcp.flowercomputer.com

No auth detected

MCP server metadata

Name: flower-company-information-and-published-content
Version: 0.1.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Flower Company Information and Published Content MCP is unauthenticated and read-only: it cannot write, mutate, publish, authenticate, or access private data. Start with `get_company_overview({})` as the first call for Flower's canonical company information and links. Use the other tools only for their advertised public content or API-status purposes. If returned content is marked historical or outdated, treat it as historical context rather than current fact, and preserve the returned canonical URLs when citing it.

Known tools 6

get_company_overview

Use when an agent needs Flower's canonical description, mission, current or prior work, public links, or high-level contact data.

Inferred read-only

list_posts

Use to browse Flower's published posts or discover valid slugs before calling get_post.

Inferred read-only

get_post

Use when an agent already has a published Flower slug and needs the full Markdown article.

Inferred read-only

search_posts

Use to search Flower post metadata by title, excerpt, category, author, tag, or slug when a full article body is not needed.

Potential side effects

get_contact_information

Use when an agent needs Flower's canonical public contact details and public links without the full company overview.

Inferred read-only

get_api_status

Use when an agent needs to check availability and version of Flower's public content API.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.flower-company-information-and-published-content]
url = "https://mcp.flowercomputer.com"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "flower-company-information-and-published-content": {
      "type": "http",
      "url": "https://mcp.flowercomputer.com"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: flower-company-information-and-published-content
Remote MCP URL: https://mcp.flowercomputer.com

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "flower-company-information-and-published-content": {
      "url": "https://mcp.flowercomputer.com"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "flower-company-information-and-published-content": {
      "type": "http",
      "url": "https://mcp.flowercomputer.com"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "flower-company-information-and-published-content",
  "transport": "streamable-http",
  "url": "https://mcp.flowercomputer.com"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.