# Globster Developer Guide

Globster is by monday.com.

Build with the Globster Plugin SDK, connect MCP servers, and share custom plugins through your own marketplace. Build around your tools, with scoped credentials and human approvals.

## Connect an MCP Server

Use MCP when your internal service already exposes tools through the Model Context Protocol.

1. Choose a Streamable HTTP server or a stdio process supported by the agent’s runtime.
2. Configure the connection and credential references. Test tool discovery before enabling it.
3. Review the exposed tools, approve the connection changes, and enable the connection for the selected agent.

The MCP engine does not perform an OAuth login for arbitrary servers or guess legacy SSE endpoints. Managed app authorization is a separate connection flow. Availability depends on installed capabilities and network policy.

## Build With the Plugin SDK

Use a plugin when your integration needs its own tool definitions, logic, configuration, or lifecycle.

1. Build a Python plugin with the Globster Plugin SDK. Define focused tools with clear inputs, outputs, and expected side effects.
2. Declare your plugin’s version, SDK compatibility, and dependencies in plugin.toml. Register tools through the SDK and package your release with agent-plugin pack.
3. Test with a limited account and representative requests. Review credentials, approval behavior, and deployment compatibility before rollout.

The Plugin SDK exists today. Contact our team for SDK access and the supported development setup. Custom tools remain subject to the agent’s permissions and runtime policy.

## Create a Private Marketplace

Use a custom marketplace source to distribute the plugins and versions your team has reviewed.

1. Package and version your plugins. Publish a catalog with their descriptions, compatibility requirements, and release artifacts.
2. Connect your marketplace source to the intended agents. Keep internal packages on hosting with appropriate access controls.
3. Review installation and upgrade plans before rollout. Plugin compatibility and artifact integrity are checked during installation.

Custom marketplace sources are supported today. Private access requires suitable hosting and a permitted network path; contact us to agree the setup for your organization.

## Teach a Reusable Skill

Use a skill when the tools already exist and the agent needs a repeatable procedure or your team’s standards.

1. Give the skill a clear name and a description of when to use it.
2. Write concise instructions, the expected result, and the points that need human review.
3. Try the skill on a real example, review the output, and refine the instructions. The agent’s tool permissions still apply.

Skills guide behavior; they do not grant access or execute code by themselves. The native harness supports SKILL.md files, and installed skill-management capabilities can manage user-authored skills.

## Example Skill

```markdown
---
name: customer-brief
description: Prepare a customer brief before an account meeting
---

Summarize the account using its authorized sources.
Link the evidence and flag missing information.
Draft next steps for the account owner to review.
```

## Coming Soon

More ways to build with Globster are on the way. These platform capabilities are planned and not yet available.

### Official Platform MCP: Coming Soon

Connect compatible AI tools to Globster through an official MCP interface.

### Official Platform API: Coming Soon

Integrate Globster into your own applications and services.

### Official Platform CLI: Coming Soon

Work with Globster from your terminal and development workflows.

### Agent Registration: Coming Soon

Register agents through a supported developer flow.

## Which Extension Should I Choose?

Choose a managed app connection for an existing supported service, MCP for a tool server, a custom plugin for integration logic, and a skill for reusable instructions. These can work together.

## Where Do Credentials Belong?

Use configured credential bindings and provider authorization. Keep passwords and tokens out of prompts, skill files, examples, and source code. Access remains subject to the connected account and agent configuration.

## Does an MCP Connection Bypass Approvals?

No. Discovered MCP tools enter the ordinary tool registration and approval path. Tool annotations, configured policy, and any applicable grants determine whether an action needs review.

## Can I Develop My Own Plugin With the SDK?

Yes. The Globster Plugin SDK supports custom Python plugins with tools, configuration, and lifecycle behavior. Contact our team for SDK access and the supported setup for your organization.

## Can Our Team Have a Private Marketplace?

Yes. Custom marketplace sources let you maintain your own plugin catalog and versioned releases. Private distribution needs appropriate hosting, access controls, and connectivity. We’ll help you plan a supported setup.

## Are the Official Platform MCP, API, and CLI Available?

Coming soon. The official platform MCP, API, CLI, and agent registration are planned and are not available through this guide yet. The existing Plugin SDK and connections to external MCP servers are separate capabilities you can use today.

[Discuss an integration](https://globster.ai/book-demo/)