Streamline Agent Plugins

Plugins that bring Streamline icons, illustrations and design elements to AI agents. Each plugin bundles the Streamline MCP server with skills that teach the agent how to use it well.

Plugins

Install in Claude Code

/plugin marketplace add webalys-hq/agent-plugins
/plugin install streamline-icons@streamline-icons

If you added this marketplace before, refresh it first:

/plugin marketplace update streamline-icons

The Streamline tools work without an account for searching and free assets. Sign in with your Streamline account when prompted to download premium assets.

Install in Cursor

Install Streamline Icons from the Cursor Marketplace. It works without an account; sign in with your Streamline account when Cursor asks, to download premium assets.

ChatGPT and Codex

The plugin is packaged for OpenAI with the portable Agent Plugins layout: plugin.json at the plugin root, with the ChatGPT listing copy under extensions["com.openai"]. Keep that copy in line with the plugin guidelines: no superlatives, comparisons, testimonials or pricing. mcp.json at the plugin root declares the Streamline MCP server for OpenAI.

To build the archive for Plugins → + → Upload plugin in ChatGPT, zip the plugin folder's contents so plugin.json, mcp.json, skills/ and assets/ sit at the archive root. The upload fails with "Invalid plugin package" when they are inside a top-level folder.

cd plugins/streamline-icons && rm -f ../streamline-icons.zip && zip -qr ../streamline-icons.zip . -x '*.DS_Store' '.mcp.json' '.claude-plugin/*' '.cursor-plugin/*'

The rm matters: zip adds to an existing archive, so without it files you deleted from the plugin stay in the zip. The Claude and Cursor files are left out because OpenAI reads .mcp.json as an MCP connection too.

The OpenAI dashboard rejects the upload unless:

• name in plugin.json matches the plugin you are updating (streamline-icons).
• shortDescription (the subtitle) is 30 characters or fewer.
• version in plugin.json differs from the last uploaded one. Bump it for every update.
• supportURL and logo are set.
• The root mcp.json declares the Streamline MCP server. Removing it from an existing plugin isn't supported.

Skills are copied into the archive at upload, so re-zip and re-upload after changing them.

Only one plugin can connect to the Streamline MCP server, and the server's domain-verification token (/.well-known/openai-apps-challenge) comes from the NX_BACKEND_OPENAI_APPS_CHALLENGE_VERIFICATION_CODE env var in streamline-api-nestjs. A new plugin needs its token set there and the public API redeployed.

MCP Registry listing

mcp-registry/server.json is the Streamline MCP server's entry in the official MCP Registry, published as com.streamlinehq/mcp. It used to live in webalys-hq/streamline-mcp.

To publish a change:

1. Bump version in server.json. The registry rejects a version it already has.
2. Push a tag named mcp-v<version>, for example mcp-v2.0.1. The Publish to MCP Registry workflow publishes it.

The workflow signs in to the registry with DNS authentication on streamlinehq.com, using the MCP_DNS_PRIVATE_KEY repository secret. GitHub sign-in only grants the io.github.webalys-hq/* namespace, so it can't publish com.streamlinehq/mcp. See DNS authentication to

... View full README on GitHub