Niche Mcp Kit

Stage Linear, Notion, Figma MCP safely.

Skill metadata


Source	Bundled (installed by default)
Path	`skills/devops/niche-mcp-kit`
Version	`1.0.0`
Author	VibeOS
License	MIT
Tags	`mcp`, `linear`, `notion`, `figma`, `cursor`, `saas`, `c8`
Related skills	`saas-mcp-onboarding`, `mcp-safe-hygiene`, `figma-edit`, `notion`, `design-to-code-loop`, `analytical-ui`

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Niche MCP Kit Skill

Operator cookbook for Cursor-style niche SaaS MCP (Linear / Notion / Figma) without growing VibeOS core. Catalog entries already ship under optional-mcps/; this skill is the safe enable path (C8).

When to Use

Product / design / PM workflows that need tickets, docs, or design context
After vibeos tools / vibeos mcp list when an operator asks for Linear/Notion/Figma
When Russia/geo blocks Linear OAuth — use the staged-disabled path

Prerequisites

vibeos mcp CLI available
Secrets only in ~/.vibeos/.env (never in yaml)
Skill mcp-safe-hygiene for tools.include discipline
Optional: skill saas-mcp-onboarding for Linear deep-dive

How to Run

# Discover catalog (bundled)
vibeos mcp list
vibeos mcp info figma
vibeos mcp info notion
vibeos mcp info linear

# Install (writes mcp_servers entry; often starts with tools.include from catalog)
vibeos mcp install figma
vibeos mcp install notion
# Linear: install may stay enabled:false until OAuth works from your network
vibeos mcp install linear

# Tighten tools after OAuth discovery
vibeos mcp configure figma
vibeos mcp configure notion

# Hygiene
vibeos mcp audit
vibeos doctor

Reference yaml snippets: examples/mcp/README.md in the repo.

Quick Reference

Need	Path	Notes
Design tokens in code	skill `design-to-code-loop` + Figma MCP	MCP for live file context; skill for CSS vars
Edit Figma via API	optional skill `figma-edit`	Needs `FIGMA_ACCESS_TOKEN` in `.env`
Notion pages/DB	MCP `notion` or skill `notion`	Prefer MCP when catalog OAuth works
Linear issues	MCP `linear`	OAuth; may need VPN outside Linear's regions
Automations	MCP `n8n`	Needs `N8N_*` in `.env`
GitHub	catalog `github`	Catalog present; OAuth opt-in (Timeweb path default)

Procedure

1. Prefer catalog install over hand-written yaml

vibeos mcp install <name>

Hand-copy from examples/mcp/README.md only when you need enabled: false staging before first OAuth.

2. Figma (design → agent)

vibeos mcp install figma → OAuth to Figma
vibeos mcp configure figma → enable read tools first (no silent writes)
For token extraction without Figma live: skill design-to-code-loop
For mutations / exports via REST: optional figma-edit + FIGMA_ACCESS_TOKEN

Catalog default_enabled is empty on purpose — operator opts in after OAuth.

3. Notion (docs → agent)

vibeos mcp install notion (HTTP + OAuth per catalog)
Restrict tools.include to read/list tools before any write tools
If MCP OAuth fails, fall back to bundled skill notion (API token in .env)

4. Linear (tickets → agent)

Stage disabled if geo-blocked:

mcp_servers:
  linear:
    url: https://mcp.linear.app/mcp
    auth: oauth
    enabled: false
    tools:
      include: [list_issues, get_issue, list_projects, get_project, list_teams]

From a network that can reach Linear OAuth: set enabled: true, run OAuth
Expand tools only via vibeos mcp configure linear
Never add write/create tools until read path is proven

5. Footprint rules (do not violate)

No new in-tree plugins/ for Linear/Notion/Figma SaaS products
No GitHub MCP enable while the project ships without GitHub
No new core tools — MCP + skills only
Secrets stay in .env; behavioral flags in config.yaml

Pitfalls

Empty tools.include after install → model may see a huge MCP schema; always configure
Linear OAuth 403 / timeout from some regions → keep enabled: false, use VPN later
Confusing Figma MCP with figma-edit skill — MCP is conversation tools; skill is REST scripts
Enabling GitHub MCP “just in case” fights the Timeweb-only release policy

Verification

vibeos mcp list
vibeos mcp audit
vibeos doctor
# Optional: vibeos adoption status  (catalog / staged checks)

Expect: installed servers show in list; audit clean; no credential leakage in yaml.

Skill metadata​

Reference: full SKILL.md​

Niche MCP Kit Skill

When to Use​

Prerequisites​

How to Run​

Quick Reference​

Procedure​

1. Prefer catalog install over hand-written yaml​

2. Figma (design → agent)​

3. Notion (docs → agent)​

4. Linear (tickets → agent)​

5. Footprint rules (do not violate)​

Pitfalls​

Verification​