Master Framework

Overview
Team Structure
Culture
HR
Developers and QA
Plugs and Growth: viaSocket
Growth : viaSocket
Partnership: viaSocket
Support Team
Agency partners (hold)
Marketing #hold
Tools We Use
MCP
Embed
Webinar
Investor
Custom GPTs
Automation book
AI Prompts that we are using
Automation Challenges with Solutions.
Automation Experts Guidelines
Automation Intern Training.
Automation Incentive Programme
viasocket-departments-criteria
Active Paid Subscriptions
DocStarBuilt with DocStar
  1. /
  2. MCP

MCP

#

đź§© Purpose & Mission

The MCP team is responsible for building, maintaining, and expanding viaSocket’s public Marketplace, where plugins, automations, and templates are showcased—and the Community Platform, where users and developers collaborate, share, and engage.


#

🛠️ Core Responsibilities

  • Build and maintain the viaSocket Marketplace interface (public + internal views)

  • Enable search, filter, and category-based discovery of plugins, templates, and workflows

  • Integrate plugin versioning, reviews, author metadata, and usage statistics

  • Support monetization modules (in future roadmap) for paid plugins or premium listings

  • Manage submission and approval workflows for community-generated content

  • Build a robust Community section with Q&A, changelogs, discussions, and upvotes

  • Facilitate public profiles for developers and companies

  • Connect GitHub, Notion, and Docs integrations to community content pipelines

  • Improve SEO and visibility for public-facing content

  • Track content moderation, abuse reports, and support ticket integration


#

đź§± Collaborations

  • Plugin Team: for real-time plugin data, ratings, and usage metrics

  • Growth Team: for marketplace visibility campaigns and SEO strategy

  • Design Team: for UX consistency across listings, tiles, and profiles

  • QA Team: for checking broken links, misclassified plugins, UI regression

  • Support Team: for flagging or moderating submitted content


#

⚙️ Tools & Stack

  • Languages: JavaScript, TypeScript, Python

  • Frameworks: React, Next.js

  • Search: Algolia (Marketplace Search & Indexing)

  • CMS: Notion API / Internal Content DB

  • Auth: viaSocket Auth + GitHub OAuth

  • Moderation Tools: Custom dashboards, Admin flows

  • Data Handling: REST APIs, GraphQL for dynamic content

  • Hosting: Vercel / Netlify

  • Testing: Cypress, Playwright, Manual Curation QA

  • Docs: Internal Notion, Public Help Center, GitHub Discussions
























Was this helpful?
DocStarBuilt with DocStar
Was this helpful?