3,400+ MCP servers ready to use
Vinkius

ChurchStamp MCP Server for VS Code CopilotGive VS Code Copilot instant access to 10 tools to Check Churchstamp Status, Create Campaign, Create Contact, and more

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The ChurchStamp app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 10 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install ChurchStamp and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "churchstamp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
ChurchStamp
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About ChurchStamp MCP Server

Connect your ChurchStamp account to any AI agent and take full control of your physical direct mail orchestration and automated postcard outreach through natural conversation.

GitHub Copilot Agent mode brings ChurchStamp data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Postal Outreach Orchestration — Programmatically send personalized postcards and letters to recipients, retrieving detailed technical status in real-time
  • Campaign Intelligence — Programmatically retrieve lists of active direct mail campaigns and access complete performance metadata for your mobile outreach
  • Design Portfolio Architecture — Access your complete directory of mail designs and templates to maintain a perfectly coordinated brand presence
  • Delivery Monitoring — Access real-time status updates for mail pieces and track campaign progress directly through your agent for instant operational reporting
  • Infrastructure Verification — Verify account-level API connectivity and monitor mailing volume directly through your agent for perfectly coordinated service scaling

The ChurchStamp MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 10 ChurchStamp tools available for VS Code Copilot

When VS Code Copilot connects to ChurchStamp through Vinkius, your AI agent gets direct access to every tool listed below — spanning direct-mail, postcard-marketing, automated-outreach, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

check_churchstamp_status

Verify ChurchStamp API connectivity

create_campaign

Optionally assign a design template. Create a mail campaign

create_contact

Add a contact

get_campaign

Get campaign details

get_design

Get design details

get_user_details

Get your account

list_campaigns

List all mail campaigns

list_contacts

List all contacts

list_designs

List all postcard designs

send_mail

Send a postcard

Connect ChurchStamp to VS Code Copilot via MCP

Follow these steps to wire ChurchStamp into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using ChurchStamp

Ask Copilot: "Using ChurchStamp, help me...". 10 tools available

Why Use VS Code Copilot with the ChurchStamp MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with ChurchStamp through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

ChurchStamp + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the ChurchStamp MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for ChurchStamp in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with ChurchStamp immediately.

01

"Send a 'Welcome Postcard' (Design ID: ds_123) to 'John Doe' at '123 Main St, London, SW1A 1AA'."

02

"List all active direct mail campaigns in my ChurchStamp account."

03

"Show my available mail designs and templates."

Troubleshooting ChurchStamp MCP Server with VS Code Copilot

Common issues when connecting ChurchStamp to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

ChurchStamp + VS Code Copilot FAQ

Common questions about integrating ChurchStamp MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.