Internal tool · Next.js

hq.profitway.pl

The agency's internal system, for people and for AI tools

A panel for the whole Profitway team: brand materials, everyday tools and two MCP servers that give AI assistants such as Claude and Cursor direct access to the brand book and the company's technical documentation. Sign-in with Google, limited to company accounts.

Role: Main developer: 213 of 244 commits
Period: Feb - Oct 2026
Stack: Next.js 16
React 19
TypeScript
Tailwind CSS 4
Auth.js
next-intl
MCP
Vitest
Docker

What the panel serves

Sign-in
1. Google account
2. Company domain only
For people
1. Brandland
2. Devland
3. Directory
4. Email signatures
5. Job postings
6. Vault
For AI tools
1. Brand book MCP · 19 tools
2. IT docs MCP · 10 tools

One Next.js app, deployed in Docker.

modules: 6
tools in 2 MCP servers: 29
automated tests in CI: 167
interface, installable as an app: PL / EN

Context

The agency needed one place for its brand assets and everyday tools, usable by employees and by the AI assistants the team works with every day.

In September 2026 the panel moved from office.profitway.pl to hq.profitway.pl. Old addresses redirect to the new domain with the path kept, so saved links keep working.

What I did

Brandland: the brand book as PDF, a logo and sign configurator exporting SVG, PNG and JPG, colours, typography with a font pack, icons and Lottie animations exported to GIF and MP4
Devland: design-system files prepared for AI tools and step-by-step MCP setup for the team
Employee directory read from Google Workspace, with roles kept in configuration
Email signature generator producing ready HTML signatures
Job postings with a WYSIWYG editor for admins and a public JSON feed
Vault: passwords encrypted in the browser before they are stored, shareable with clients who have no account
The whole panel in Polish and English, installable on a phone as a PWA
A public brand book MCP server: anyone can connect Claude or Cursor to Profitway's colours, typography, logos, components and email templates

Brand book MCP · 19 tools

The public MCP server exposes the brand book as tools. An AI assistant asks for exact colours, tokens or a logo instead of guessing them.

get_brand_colors
get_typography
get_logo
get_logo_guidelines
get_icons
get_icon_guidelines
get_animation_guidelines
get_keyframes
get_tailwind_tokens
get_token
get_shadcn_setup
get_full_design_system
get_design_doc
get_component
list_components
list_assets
get_email_template
list_email_templates
get_llms

Hard parts and how I solved them

Problem
AI assistants could not see the brand rules or the IT documentation, so the team pasted them into prompts by hand.
Solution
Two MCP servers built as stateless Streamable HTTP route handlers inside the same Next.js app: the brand book with 19 tools from the agency's design library, and the IT documentation with 10 tools that read a private repository live.
Problem
The codebase grew fast and by September had no CI, no tests and a broken lint step.
Solution
A planned refactor: shared UI primitives, one MCP channel per server and a CI pipeline that runs lint, type checking, 167 tests and the build on every pull request.
Problem
Moving the panel to a new domain without breaking bookmarks and integrations.
Solution
Permanent redirects from the old domain that keep the path, done and closed within four days.