Pixelesq
com.pixelesqPublished by pixelesq.comv1.0.1Updated Oct 28, 2026
Build and manage Pixelesq websites from a conversation: pages, sections, content, SEO, analytics.
Overview
Build and manage Pixelesq websites from a conversation: pages, sections, content, SEO, analytics and publishing.
- What you can do
- List projects, pages, collections, partials, forms, assets and domains, and read page content and revisions
- Create, duplicate, edit, publish, unpublish, revert and delete pages, sections and partials
- Write and publish collection entries, and change collection schemas
- Tune SEO: page metadata, Search Console performance, index status, URL inspection and redirects
- Read site analytics, AI referral traffic and form submissions
- Restyle the theme, upload or generate images, and search stock images
- When to use it
- Use it when the user runs a site on Pixelesq and wants an assistant to draft or restructure pages, write content, adjust SEO and redirects, review traffic, or publish changes without leaving the chat.
- Requirements
- Remote MCP endpoint with OAuth 2.1 (PKCE) sign-in using Google or a Pixelesq email code. A Pixelesq account with at least one project is required. Scopes are granted at sign-in: projects:read, content:read, content:write, publish, analytics:read. Some clients are offered 67 of the 70 tools, with AI image generation withheld.
Installation
In SourceWeft
- Open Pixelesq in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.pixelesq%2Fpixelesq/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"pixelesq": {
"type": "http",
"url": "https://mcp.pixelesq.app/mcp"
}
}
}README
Pixelesq Agent Skills
Manage websites built on Pixelesq from any AI agent. Build and edit pages section by section, write content into collections, tune SEO and structured data, read Search Console and site analytics, manage redirects and images, restyle the theme, and publish when the user says so.
This repository is three things at once:
- Seven skills in the Agent Skills format, loaded by Claude Code, Cursor, Codex, Copilot, Gemini CLI, Goose and other compatible agents.
- Four specialist agents for Claude Code (and any platform that reads
agents/*.md). - The Pixelesq MCP connector, declared in
.mcp.json:https://mcp.pixelesq.app/mcp, 70 tools, OAuth sign-in with your Pixelesq account.
Install
Claude Code (plugin)
Then run /mcp and sign in to Pixelesq. The skills load on demand, the agents are available as @pixelesq:site-manager, @pixelesq:seo-specialist, @pixelesq:content-strategist and @pixelesq:design-consultant, and the connector is registered from .mcp.json.
Claude Code (connector only)
Claude.ai and Claude Desktop
Settings, Connectors, Add custom connector, paste https://mcp.pixelesq.app/mcp, sign in.
ChatGPT
Open Pixelesq in the ChatGPT plugin directory and connect; that listing uses https://pixelesq-mcp.pixelesq.workers.dev/mcp, the same server on its older address. To add the server by hand: Settings, turn on Developer mode (under Apps or Security and login), then Plugins, +, Add custom MCP server, paste https://mcp.pixelesq.app/mcp, set authentication to OAuth and install it. A connection made on one address does not carry over to the other.
Cursor
Add the server to mcp.json:
VS Code
Other platforms
Clone the repository, point the agent's skills directory at skills/, and configure the MCP server URL https://mcp.pixelesq.app/mcp. Clients register dynamically or present a client ID metadata document; both are accepted.
Sign-in and scopes
The connector uses OAuth 2.1 with PKCE. Sign in with Google or with a Pixelesq email and the code it sends. A Pixelesq account with at least one project is required; sign up at https://app.pixelesq.ai.
Scopes are granted at sign-in and stamped into the token: projects:read, content:read, content:write, publish, analytics:read. A tool outside the grant answers with a refusal that asks the client to reconnect.
How edits stay safe
- Saves to pages, sections, headers, footers and entries change a draft, and
publish_page,publish_partialandpublish_entrymake it live. A few writes change the live site right away:update_page_metaon a published page, the redirect tools,update_collection_schema,update_entry(a new name shows in listings),delete_page,delete_entry,update_theme(unlesspublish: false) andupdate_form_schema(a form has no draft). The skills tell the agent to confirm before any of these. - Every save carries the
lastVersionfrom the read before it; a stale version is refused instead of overwriting someone else's work. - A publish carries
expectedRevisionIdandexpectedHeadAnchorfrom the read the user reviewed, and refuses if the draft moved. - Saves merge field by field, arrays replace whole,
nullclears a field. The agent only touches what the user asked for. - Structural section edits (insert, remove, reorder, bind) take an
idempotencyKeyso a lost answer can be retried safely.
Skills
Agents
The 70 tools
Claude.ai, Claude Desktop and Cowork are offered 67 of these: the three AI image generation tools are withheld there, and in Claude Code unless its connection was registered dynamically. Other clients can get all 70. Read tools change nothing; write tools carry the hints that let clients ask before running them.
Repository layout
Keeping it current
- The section guides are generated. Refresh
skills/website-management/references/section-catalog.jsonfrom the connector'slist_section_types(all groups, full detail), then runnode scripts/generate-section-guide.mjs. - The tool map mirrors the connector's README, which is generated from the tool registry.
- Validate before publishing:
claude plugin validate . - The ChatGPT plugin is updated with a ZIP on the OpenAI Plugins page (Upload plugin to make changes): run
npm run submission:chatgptin pixelesq-mcp, thennode scripts/build-openai-bundle.mjshere writesdist/pixelesq-chatgpt-<version>.zip(the plugin manifest,mcp.json, the skills, the icon and the listing screenshots).
Links
- Pixelesq
- Connector documentation
- Agent Skills
- Model Context Protocol
- Privacy policy and terms
- Support: [email protected] · Help center
License
MIT
Source: README.md at commit 8d9c0dc
Tools
0Version history
2- v1.0.1LatestOct 17, 2026
- v1.0.0Sep 16, 2026
Score
85% 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
- Documentation15 pts
- License10 pts