Files
hermes-mcp/product/site/index.html
Garfield 73f83c0d86 feat: WhatsApp + LinkedIn integrations, SquareMCP rebrand, opencode docs
WhatsApp Business API (Meta Cloud API)
- New client: src/clients/whatsapp.ts
- Tools: whatsapp_send_message, whatsapp_send_template, whatsapp_list_templates
- REST endpoints: POST /api/whatsapp/send, POST /api/whatsapp/template, GET /api/whatsapp/templates
- Multi-account env var pattern: WHATSAPP_{ACCOUNT}_*

LinkedIn API (OpenID Connect)
- New client: src/clients/linkedin.ts
- Tools: linkedin_get_profile, linkedin_create_post, linkedin_search_connections, linkedin_send_message
- REST endpoints: GET /api/linkedin/profile, POST /api/linkedin/post, POST /api/linkedin/search-connections, POST /api/linkedin/message
- Multi-account env var pattern: LINKEDIN_{ACCOUNT}_*
- Uses /v2/userinfo (OpenID Connect) for profile reads

Domain migration
- hermes.fetcherpay.com -> hermes.squaremcp.com
- Updated K8s ingress, TLS cert, SERVER_URL env var
- Updated OPENCODE.md and opencode.json references

SquareMCP site
- Added logo assets (SVG, LinkedIn variants)
- Added terms.html
- Updated Dockerfile, nginx config, styles, index, privacy pages

Docs
- Added OPENCODE.md for opencode AI integration setup
- Updated .env.example with WhatsApp and LinkedIn credentials
- Added opencode.json to .gitignore (contains live API key)

Total tools: 19 (email 6, obsidian 5, whatsapp 4, linkedin 4)
2026-05-05 01:25:26 -04:00

306 lines
12 KiB
HTML

<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>SquareMCP</title>
<meta
name="description"
content="SquareMCP is a managed MCP gateway for internal tools with authentication, permissions, audit logs, and observability."
/>
<link rel="stylesheet" href="./styles.css?v=20260505b" />
</head>
<body>
<nav class="topbar">
<div class="wrap topbar-row">
<a class="brand" href="/">
<img class="brand-logo" src="./squaremcp-logo.svg" alt="" />
<span class="brand-text">SquareMCP</span>
</a>
<div class="topbar-actions">
<a class="topbar-link" href="#pricing">Pricing</a>
<a class="topbar-link" href="#pilot-form">Pilot intake</a>
<a class="button secondary" href="mailto:info@squaremcp.com">Contact</a>
</div>
</div>
</nav>
<header class="hero">
<div class="wrap hero-grid">
<div class="hero-copy">
<div class="eyebrow">Managed MCP infrastructure</div>
<h1>SquareMCP for secure internal tool access</h1>
<p class="lede">
Let AI agents work with your internal systems without bypassing operating controls.
SquareMCP gives teams a managed MCP layer for authentication, permissions, audit
logs, and production visibility from day one.
</p>
<div class="hero-points">
<span>Fast pilot deployment</span>
<span>Tool-level controls</span>
<span>Audit-ready access</span>
</div>
<div class="hero-contact">
Contact:
<a href="mailto:info@squaremcp.com">info@squaremcp.com</a>
</div>
<div class="actions">
<a class="button primary" href="#pilot-form">Book a pilot</a>
<a class="button secondary" href="#pricing">View pricing</a>
</div>
</div>
<section class="hero-panel" aria-labelledby="pilot-preview-title">
<div class="hero-media">
<img
id="heroAnimation"
src="./squaremcp_launch.gif"
data-animated-src="./squaremcp_launch.gif"
data-poster-src="./squaremcp_launch_poster.png"
data-play-ms="9600"
alt="SquareMCP launch storyboard preview"
width="728"
height="410"
/>
</div>
<div class="panel-topline">Typical first deployment</div>
<h2 id="pilot-preview-title">Internal support copilot with safe system access</h2>
<ul class="signal-list">
<li>
<strong>Connectors:</strong>
REST APIs, Postgres, internal operations tools
</li>
<li>
<strong>Controls:</strong>
allowlists, deny lists, revocation, access boundaries
</li>
<li>
<strong>Visibility:</strong>
request logs, usage traces, deployment-level audit history
</li>
</ul>
<div class="metric-row">
<div class="metric">
<span class="metric-value">1 day</span>
<span class="metric-label">first safe endpoint</span>
</div>
<div class="metric">
<span class="metric-value">$5k+</span>
<span class="metric-label">pilot setup range</span>
</div>
</div>
</section>
</div>
</header>
<main>
<section class="band">
<div class="wrap section-head">
<div>
<div class="kicker">Why teams buy</div>
<h2>Put agent access behind a layer your team can operate</h2>
</div>
<p class="section-copy">
The buyer does not want another framework to assemble. They want a managed path to
exposing internal tools to agents without opening production systems up blindly.
</p>
</div>
<div class="wrap feature-grid">
<article class="feature">
<h3>Authentication</h3>
<p>Give agents access through API keys and OAuth flows that can be rotated and revoked.</p>
</article>
<article class="feature">
<h3>Tool permissions</h3>
<p>Expose only the tools a workspace should use, with visibility into who can call what.</p>
</article>
<article class="feature">
<h3>Audit logs</h3>
<p>Track every tool call so operators and regulated teams can review activity later.</p>
</article>
<article class="feature">
<h3>Observability</h3>
<p>See request volume, connector activity, and operational failures before pilots go sideways.</p>
</article>
</div>
</section>
<section class="band alt">
<div class="wrap section-head">
<div>
<div class="kicker">Ideal buyers</div>
<h2>Built for internal copilot teams first</h2>
</div>
<p class="section-copy">
The cleanest first wedge is internal support and operations copilots, where ROI is
easier to prove and governance matters early.
</p>
</div>
<div class="wrap buyer-grid">
<article class="buyer-card">
<h3>AI startups</h3>
<p>Need internal tool access quickly without building a full security layer from scratch.</p>
</article>
<article class="buyer-card">
<h3>Mid-market internal AI teams</h3>
<p>Need a controlled bridge between copilots and the systems employees already use.</p>
</article>
<article class="buyer-card">
<h3>Fintech and regulated teams</h3>
<p>Need logs, permissions, and operating discipline before exposing sensitive workflows.</p>
</article>
</div>
</section>
<section id="pricing" class="band">
<div class="wrap section-head">
<div>
<div class="kicker">Packaging</div>
<h2>Start with a paid pilot, then grow into recurring revenue</h2>
</div>
<p class="section-copy">
The early offer is a managed deployment, not a self-serve platform sale. Close pilots,
then learn which security and connector features unblock larger contracts.
</p>
</div>
<div class="wrap pricing-grid">
<article class="pricing-card">
<div class="pricing-tier">Pilot</div>
<div class="pricing-price">$5k-$10k setup</div>
<p class="pricing-copy">$500-$3k monthly once the initial deployment is live.</p>
<ul class="list">
<li>Hosted MCP endpoint</li>
<li>Auth and connector setup</li>
<li>Tool filtering and logs</li>
<li>Delivery support</li>
</ul>
</article>
<article class="pricing-card">
<div class="pricing-tier">Team</div>
<div class="pricing-price">$199-$499/mo</div>
<p class="pricing-copy">For smaller internal AI teams evaluating managed MCP access.</p>
<ul class="list">
<li>Up to 10 connectors</li>
<li>Role-based permissions</li>
<li>Audit logs</li>
<li>Email support</li>
</ul>
</article>
<article class="pricing-card">
<div class="pricing-tier">Business</div>
<div class="pricing-price">$1.5k-$3k/mo</div>
<p class="pricing-copy">For production deployments with stronger operating requirements.</p>
<ul class="list">
<li>SSO</li>
<li>Private networking</li>
<li>Longer retention</li>
<li>Alerts and SLA</li>
</ul>
</article>
</div>
</section>
<section id="pilot-form" class="band">
<div class="wrap form-grid">
<div>
<div class="kicker">SquareMCP pilot intake</div>
<h2>Collect a serious pilot request, not just an email click</h2>
<p class="section-copy">
This intake form builds a ready-to-send pilot request with the details you actually
need to qualify a first deployment for squaremcp.com.
</p>
</div>
<form class="pilot-form" id="pilotIntakeForm">
<input type="hidden" name="submission_tag" value="" />
<div class="field-grid">
<label>
<span>Name</span>
<input name="name" type="text" required />
</label>
<label>
<span>Work email</span>
<input name="email" type="email" required />
</label>
<label>
<span>Company</span>
<input name="company" type="text" required />
</label>
<label>
<span>Role</span>
<input name="role" type="text" required />
</label>
<label>
<span>Primary use case</span>
<select name="use_case" required>
<option value="">Select one</option>
<option>Internal support copilot</option>
<option>Operations workflow assistant</option>
<option>Internal developer tooling</option>
<option>Regulated knowledge access</option>
<option>Other</option>
</select>
</label>
<label>
<span>Expected timeline</span>
<select name="timeline" required>
<option value="">Select one</option>
<option>Within 2 weeks</option>
<option>This month</option>
<option>This quarter</option>
<option>Exploring only</option>
</select>
</label>
</div>
<label>
<span>Internal systems to connect</span>
<textarea
name="systems"
rows="4"
placeholder="Examples: Postgres, Zendesk, internal REST APIs, admin workflows"
required
></textarea>
</label>
<label>
<span>Security or compliance requirements</span>
<textarea
name="requirements"
rows="4"
placeholder="Examples: audit logs, SSO, network isolation, approval flows"
required
></textarea>
</label>
<div class="form-actions">
<button class="button primary" type="submit">Submit pilot request</button>
<button class="button secondary" type="button" id="copyRequestButton">Copy request</button>
</div>
<div class="form-output" id="pilotOutput" aria-live="polite">
Fill out the form to submit your SquareMCP pilot request.
</div>
</form>
</div>
</section>
</main>
<footer class="footer">
<div class="wrap footer-row">
<div>
<strong>SquareMCP</strong>
<span class="footer-copy">Managed MCP infrastructure for internal tools.</span>
</div>
<div class="footer-links">
<a class="footer-link" href="mailto:info@squaremcp.com">info@squaremcp.com</a>
<a class="footer-link" href="https://squaremcp.com">squaremcp.com</a>
<a class="footer-link" href="/privacy">Privacy</a>
<a class="footer-link" href="/terms">Terms</a>
</div>
</div>
</footer>
<script src="./script.js?v=20260424b"></script>
</body>
</html>